Support package upgrade scenarios#436
Merged
Merged
Conversation
Member
|
Addresses ComputeCanada/puppet-magic_castle#579 for pool nodes |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Rename
skip_upgradetoupgradeand add support for three more scenarios:upgrade = "security": always upgrade to security related upgradesupgrade = "vanilla-security"upgrade packages only if the image is vanillaupgrade = "all": upgrade packages during cloud-init, alwaysThe previous scenarios still supported are:
upgrade = "vanilla-all"limit package upgrade to security related upgrades only if the image is vanilla - equivalent of previousskip_upgrade = falseupgrade = "none", never upgrade, equivalent ofskip_upgrade = true