fix(deployment): implement detection and handling of infinite redeployment loops #833
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When a deployConfig triggers consecutive deployments for a repository with the same commit sha, the
forceDeployflag will now be set to true to make Docker do a forced stack/project deployment.Use the new appConfig setting
MAX_DEPLOYMENT_LOOP_COUNT(default:3) to set, when the detection should set theforceDeploy. Set the option to0, to disable the detection logic and never setforceDeploy.