environment secret
A secret attached to a deployment environment, readable only by jobs that declare they deploy to that environment.
In more detail
It is available only after the environment's protection rules pass. That means production credentials are released only after the required reviewers approve.
Related terms
- secret — Any value that grants access, such as a password, access token or private key, and must be kept out of code and version control.
- deployment environment — A named target such as staging or production that a job declares, so GitHub can attach its own variables, secrets and protection rules.
- environment protection rule — A rule on a deployment environment, such as required reviewers, a wait timer or allowed branches, checked before a job may deploy there.
Taught in
- Securing Pipelines: Secrets Management — Continuous Integration & Continuous Delivery Pipelines
- Defining Environments in GitHub Actions — Continuous Integration & Continuous Delivery Pipelines
- Reusable Workflows: Inputs, Secrets And Outputs Across A Call — GitHub Actions (GH-200) Exam Prep
- Secrets And Variables By Scope: Precedence, Access And The REST API — GitHub Actions (GH-200) Exam Prep
- Usage, Billing And The Audit Log — GitHub Actions (GH-200) Exam Prep
- Environments: Reviewers, Wait Timers And Deployment Rules — GitHub Actions (GH-200) Exam Prep
- Full Mock And Review: Where Your Points Go — GitHub Actions (GH-200) Exam Prep