[Idea] Option to fail deployment, when app version is lower than already installed version #2336
thomasroennTRM
started this conversation in
Ideas
Replies: 1 comment
|
I agree, this should be looked into. I previously also raised this issue on #2077 (comment) |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Idea Description
Is your feature request related to a problem?
When deploying apps via AL-Go CI/CD or Publish To Environment, if the app version in app.json is lower than the version already installed on the target environment, the workflow completes successfully (green checkmark). The only indication of failure is an annotation/warning message:
This is misleading because:
Describe the solution you'd like
A new setting (e.g., failOnDowngrade or similar) in the DeployTo structure (or as a general deploy setting) that controls the behavior when a version downgrade is detected during deployment:
{ "DeployToProduction": { "EnvironmentName": "Production", "failOnDowngrade": true } }When failOnDowngrade is true, the deploy step should return an error (red/failed) instead of succeeding with only an annotation warning.
Alternatively, this could be a global deployment setting like:
{ "deployFailOnDowngrade": true }Describe alternatives you've considered
Additional context
This affects any team working with release branches or hotfix workflows where version numbers on environments may get ahead of what's in app.json on certain branches. The silent "success" makes it very difficult to catch deployment issues early.
Contribution (Optional)
All reactions