Support a charm resource to override the installed snap #149
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
|
We can't merge these changes until the workflows support file-resources on publish |
addyess
force-pushed
the
KU-1464/support-snap-version-overrides
branch
from
e38e974
to
d5eced6
Compare
addyess
force-pushed
the
KU-1464/support-snap-version-overrides
branch
from
d5eced6
to
beca4c6
Compare
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.
Overview
Create support to override the snap, while warning users they are using the charm in an override mode
Rationale
In order to test that new builds of the k8s snap will operate on the current stable k8s charm, we should be able to verify the snap before releasing it. To do so, we need a way to insert the snap into the charmed environment. This provides the ability to do so.