Commit cec6bc33 authored by Amy Qualls's avatar Amy Qualls

Merge branch 'docs-fix-ado-force-deploy-variable-name' into 'master'

Fix Auto Deploy version safety flag variable name

See merge request gitlab-org/gitlab!39926
parents b405f8d4 f07ca08a
...@@ -62,11 +62,11 @@ include: ...@@ -62,11 +62,11 @@ include:
image: "registry.gitlab.com/gitlab-org/cluster-integration/auto-deploy-image:v0.17.0" image: "registry.gitlab.com/gitlab-org/cluster-integration/auto-deploy-image:v0.17.0"
``` ```
### Ignore warning and continue deploying #### Ignore warning and continue deploying
If you are certain that the new chart version is safe to be deployed, If you are certain that the new chart version is safe to be deployed,
you can add the `AUTO_DEVOPS_ALLOW_TO_FORCE_DEPLOY_V<N>` [environment variable](customize.md#build-and-deployment) you can add the `AUTO_DEVOPS_FORCE_DEPLOY_V<N>` [environment variable](customize.md#build-and-deployment)
to force the deployment to continue, where `<N>` is the major version. to force the deployment to continue, where `<N>` is the major version.
For example, if you want to deploy the v2.0.0 chart on a deployment that previously For example, if you want to deploy the v2.0.0 chart on a deployment that previously
used the v0.17.0 chart, add `AUTO_DEVOPS_ALLOW_TO_FORCE_DEPLOY_V2`. used the v0.17.0 chart, add `AUTO_DEVOPS_FORCE_DEPLOY_V2`.
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment