feat: Rename confusing update strategies #456
Merged
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.
This PR fixes #179.
It renames
latest
strategy tonewest-build
andname
strategy toalphabetical
. If either of the old names is detected, it prints a warning message in the controller logs informing the user that the strategies have been renamed, and that support for them will be removed in future releases. Currently the old names are still honored.It also updates the documentation references for these update strategies.
Steps to test:
newest-build
oralphabetical
depending on your use case/availability of test imageslatest
orname
strategy