60 Resultados da pesquisa para "secrets"

adicionando a propriedade secrets no nível superior do arquivo, dentro do objeto JSON delimitador. Por exemplo: JSON "secrets": { "NAME_OF_SECRET_1":

for sensitive information, such as passwords, use secrets instead. For more information, see Using secrets in GitHub Actions. Defining environment variables

extremidade da API REST para segredos do GitHub Actions List organization secrets Get an organization public key Get an organization secret Create or update

compromise the self-hosted runner environment, including gaining access to secrets and the GITHUB_TOKEN which, depending on its settings, can grant write access

Although workflows from forks do not have access to sensitive data such as secrets, they can be an annoyance for maintainers if they are modified for abusive

namespace: VAULT-NAMESPACE # HCP Vault and Vault Enterprise only role: ROLE-NAME secrets: SECRET-PATH - name: Use secret from Vault run: | # This step has access

your secret using LibSodium. For more information, see "Encrypting secrets for the REST API." OAuth app tokens and personal access tokens (classic)

secret compromised. GitHub recommends the following actions for compromised secrets: Verify that the secret committed to GitHub is valid. Applies to GitHub

and provisioning profile env: BUILD_CERTIFICATE_BASE64: ${{ secrets.BUILD_CERTIFICATE_BASE64 }} P12_PASSWORD: ${{ secrets.P12_PASSWORD }} BUILD_PROVISION_PROFILE_BASE64:

fluxos de trabalho do GitHub Actions, a opção será Allow edits and access to secrets by maintainers. Permitir edições no branch de uma bifurcação que contém