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.
2,337 definitions
Brouillon de traduction automatique (French) for "Canary Release Manifest": Canary Release Manifest is a devops delivery record that lists versions, artifacts, routes, and checks for a release for small-scope production rollout. It uses commit IDs, checksums, and deployment URLs so teams can make releases auditable while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemple en brouillon: The DevOps team used Canary Release Manifest when the first traffic slice received the build, so the team could make releases auditable before the deployment window opened.”
Brouillon de traduction automatique (French) for "Artifact Rollback Plan": Artifact Rollback Plan is a devops recovery plan that defines how to return to a known good version for build output and package delivery. It uses version pins, database notes, and operator steps so teams can recover quickly from bad changes while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemple en brouillon: The DevOps team used Artifact Rollback Plan when the container image was signed, so the team could recover quickly from bad changes before the deployment window opened.”
Brouillon de traduction automatique (French) for "CI Config Drift Check": CI Config Drift Check is a devops consistency check that finds differences between intended and live configuration for continuous integration workflows. It uses desired state, live state, and diff reports so teams can avoid surprise environment behavior while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemple en brouillon: The DevOps team used CI Config Drift Check when a pull request entered the build queue, so the team could avoid surprise environment behavior before the deployment window opened.”
Brouillon de traduction automatique (French) for "Environment Build Gate": Environment Build Gate is a devops quality gate that blocks promotion when required checks fail for configuration for a runtime stage. It uses tests, lint, security scans, and policy rules so teams can prevent broken releases while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemple en brouillon: The DevOps team used Environment Build Gate when staging and production drifted, so the team could prevent broken releases before the deployment window opened.”
Brouillon de traduction automatique (French) for "Pipeline Provenance Ledger": Pipeline Provenance Ledger is a ml record that tracks where data came from and how it changed for automated data and model workflow. It uses hashes, source labels, and transformation history so teams can audit model inputs reliably while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemple en brouillon: The machine learning team used Pipeline Provenance Ledger when the pipeline missed a validation step, so the team could audit model inputs reliably before the model moved into evaluation.”
Brouillon de traduction automatique (French) for "Rollback Secret Rotation": Rollback Secret Rotation is a devops credential workflow that replaces sensitive keys without service interruption for recovery from a bad deployment. It uses dual credentials, rollout steps, and revocation so teams can reduce credential exposure while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemple en brouillon: The DevOps team used Rollback Secret Rotation when the error budget started burning, so the team could reduce credential exposure before the deployment window opened.”
Brouillon de traduction automatique (French) for "CD Approval Step": CD Approval Step is a devops workflow control that requires review before a sensitive change proceeds for deployment automation and promotion. It uses role checks, comments, and audit logs so teams can keep high-risk automation accountable while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemple en brouillon: The DevOps team used CD Approval Step when the release moved toward production, so the team could keep high-risk automation accountable before the deployment window opened.”
Brouillon de traduction automatique (French) for "Environment Artifact Signature": Environment Artifact Signature is a devops supply-chain record that proves that an artifact came from an expected build path for configuration for a runtime stage. It uses cryptographic signatures, provenance, and verification so teams can trust deployed packages while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemple en brouillon: The DevOps team used Environment Artifact Signature when staging and production drifted, so the team could trust deployed packages before the deployment window opened.”
Brouillon de traduction automatique (French) for "Environment Runbook Check": Environment Runbook Check is a devops operational test that confirms that documented procedures still work for configuration for a runtime stage. It uses dry runs, screenshots, and command validation so teams can keep response playbooks current while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemple en brouillon: The DevOps team used Environment Runbook Check when staging and production drifted, so the team could keep response playbooks current before the deployment window opened.”
Brouillon de traduction automatique (French) for "Rollback Release Manifest": Rollback Release Manifest is a devops delivery record that lists versions, artifacts, routes, and checks for a release for recovery from a bad deployment. It uses commit IDs, checksums, and deployment URLs so teams can make releases auditable while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemple en brouillon: The DevOps team used Rollback Release Manifest when the error budget started burning, so the team could make releases auditable before the deployment window opened.”