fix(resource/pipeline): fix permit_restart_from_failed_steps = false
#160
+10
−7
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
/test |
masontikhonov
requested review from
yaroslav-codefresh,
denis-codefresh and
a team
as code owners
`permit_restart_from_failed_steps` property of pipeline spec behaves differently when omit vs set to `false`. This means we should not omit `false` value while sending requests to API. Fixes #CR-26963
masontikhonov
force-pushed
the
CR-26963-fix-restart-from-failed-steps
branch
from
9ac80ec to
2adecb7
Compare
|
/test |
masontikhonov
changed the title
permit_restart_from_failed_steps to JSONpermit_restart_from_failed_steps = false
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What
This fixes
permit_restart_from_failed_steps = falsebehavior inpipelineresource.Warning
BREAKING CHANGE!
Previously,
permit_restart_from_failed_steps = falseresulted in “Permit restart pipeline from failed step: Use account settings”.From now on,
permit_restart_from_failed_steps = falsewill result in “Permit restart pipeline from failed step: Forbid”Note
In Codefresh API,
permit_restart_from_failed_steps = nullmeans “Use account settings”, andpermit_restart_from_failed_steps = falsemeans “Forbid”.However in
terraform-plugin-sdkwhich is currently in use, it is not possible to distinguish between nullish/falsy and not set value.This means, we have to choose between providing an option to FORBID restart from failed steps; and an option to inherit account settings.
We chose providing options for explicit control over pipeline resource, allowing to the end user either PERMIT or FORBID restart from failed steps.
Fixes #CR-26963
Notes
Checklist
/testcomment will be ignored by the CI trigger unless it is made by a repo admin or collaborator.