Define the new internet.
Look up the words people use online, add the ones we missed, and help make the internet easier to understand.
Look up the words people use online, add the ones we missed, and help make the internet easier to understand.
1,322 definitions
Environment Promotion is a GitOps term for moving a change from one environment to another with evidence and review. It helps teams, humans, and agents compare declared source state with running systems, then act without pretending a deployment did more than the evidence shows. Source context: OpenGitOps principles.
“The team used Environment Promotion before lunch, so the release did not sprint into production wearing untied shoes.”
Preview Environment is a GitOps term for a temporary environment used to review a change before merge or release. It helps teams, humans, and agents compare declared source state with running systems, then act without pretending a deployment did more than the evidence shows. Source context: Argo CD documentation.
“The team used Preview Environment before lunch, so the release did not sprint into production wearing untied shoes.”
Ephemeral Environment is a GitOps term for a short-lived environment created for testing, review, or validation. It helps teams, humans, and agents compare declared source state with running systems, then act without pretending a deployment did more than the evidence shows. Source context: Argo CD documentation.
“The team used Ephemeral Environment before lunch, so the release did not sprint into production wearing untied shoes.”
Progressive Delivery is a GitOps term for releasing changes gradually while watching evidence and safety signals. It helps teams, humans, and agents compare declared source state with running systems, then act without pretending a deployment did more than the evidence shows. Source context: Argo CD documentation.
“The team used Progressive Delivery before lunch, so the release did not sprint into production wearing untied shoes.”
Canary Release is a GitOps term for a release strategy that sends a small portion of traffic to a new version first. It helps teams, humans, and agents compare declared source state with running systems, then act without pretending a deployment did more than the evidence shows. Source context: Argo CD documentation.
“The team used Canary Release before lunch, so the release did not sprint into production wearing untied shoes.”
Blue Green Release is a GitOps term for a release strategy that switches between two complete environments. It helps teams, humans, and agents compare declared source state with running systems, then act without pretending a deployment did more than the evidence shows. Source context: Argo CD documentation.
“The team used Blue Green Release before lunch, so the release did not sprint into production wearing untied shoes.”
Release Evidence is a GitOps term for the logs, commits, checks, and status signals that show what changed and why. It helps teams, humans, and agents compare declared source state with running systems, then act without pretending a deployment did more than the evidence shows. Source context: OpenGitOps principles.
“The team used Release Evidence before lunch, so the release did not sprint into production wearing untied shoes.”
Audit Trail is a GitOps term for the recorded sequence of changes, approvals, and system actions. It helps teams, humans, and agents compare declared source state with running systems, then act without pretending a deployment did more than the evidence shows. Source context: OpenGitOps principles.
“The team used Audit Trail before lunch, so the release did not sprint into production wearing untied shoes.”
Commit Provenance is a GitOps term for evidence about who created a commit, when it happened, and what it changed. It helps teams, humans, and agents compare declared source state with running systems, then act without pretending a deployment did more than the evidence shows. Source context: OpenGitOps principles.
“The team used Commit Provenance before lunch, so the release did not sprint into production wearing untied shoes.”
Signed Commit is a GitOps term for a Git commit with cryptographic proof of author or system identity. It helps teams, humans, and agents compare declared source state with running systems, then act without pretending a deployment did more than the evidence shows. Source context: OpenGitOps principles.
“The team used Signed Commit before lunch, so the release did not sprint into production wearing untied shoes.”