Control init -upgrade behaviour
#1471
Open
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
- add new flag `upgradeOnInit` to API - add documentation
|
Thank you for the contribution @daniel-ciaglia ! Can you please run |
|
@akselleirv - fixed in our fork and part of the PR now. |
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.
The goal of this PR is control over the
initprocess of a given stack. ATM this is hardcoded toinit -upgradewhich force updates all provioders within their smeVer ranges if one does not use fixed versions.More background in the docs ;-)
upgradeOnInitto APIPS: If the PR is approved, squash merge would be best strategy as the history contains an unnecessary step as well.