110 Результаты поиска для "secrets"

following constructs manually: Mandatory build tools Scripted pipelines Secrets Self-hosted runners Unknown plugins For more information on manual migrations

Certain Travis CI constructs must be migrated manually. These include: Secrets Unknown job properties For more information on manual migrations, see Migrating

following: Working with the npm registry Store information in variables Using secrets in GitHub Actions Automatic token authentication About package configuration

permissions and do not have access to secrets. If your tests or other workflows triggered upon pull request require access to secrets, consider using a different

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

pipelines. These secrets must be created manually in GitHub Actions for these pipelines to function properly. For more information, see Using secrets in GitHub

protection for your own personal account, which prevents you from pushing secrets to any public repository on GitHub. For more information, see Push protection

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

signing.keychain-db # import certificate and provisioning profile from secrets echo -n "$BUILD_CERTIFICATE_BASE64" | base64 --decode -o $CERTIFICATE_PATH