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.
In more detail
The environment is a policy key: it does not create servers and does not make a deploy safe by itself. Protection rules are checked before the job starts, and only then does the job receive environment secrets.
Example
environment:
name: production
url: https://checkout.exampleRelated terms
- 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.
- environment secret — A secret attached to a deployment environment, readable only by jobs that declare they deploy to that environment.
- configuration variable — A plain, non-secret setting stored in GitHub at repository, organization or environment level and read through the vars context.
- staging — A pre-production environment set up like production, where changes are tried out before they reach real users.
Taught in
- Environments, Approvals And Checks — Microsoft Azure DevOps Engineer Expert (AZ-400) Exam Prep
- Defining Environments in GitHub Actions — Continuous Integration & Continuous Delivery Pipelines
- Environment Protection and Manual Approvals — Continuous Integration & Continuous Delivery Pipelines
- Keyless Authentication: OIDC to the Cloud — 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
- Environments: Reviewers, Wait Timers And Deployment Rules — GitHub Actions (GH-200) Exam Prep
- OIDC: Cloud Access Without Stored Keys — GitHub Actions (GH-200) Exam Prep