Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

snap_channel should be empty if resource attached #113

Closed
Pjack opened this issue Oct 18, 2024 · 1 comment · Fixed by #115
Closed

snap_channel should be empty if resource attached #113

Pjack opened this issue Oct 18, 2024 · 1 comment · Fixed by #115

Comments

@Pjack
Copy link

Pjack commented Oct 18, 2024

Follow up this suggestion in #100 (comment)

Copy link

Thank you for reporting us your feedback!

The internal ticket has been created: https://warthogs.atlassian.net/browse/SOLENG-796.

This message was autogenerated

samuelallan72 added a commit that referenced this issue Oct 20, 2024
When a resource is used, the `snap_channel` config option is ignored.
In this case, the snap is installed directly from the resource file,
so a "channel" doesn't make sense.

If `snap_channel` is set and a resource is being used,
it may indicate a confusion situation,
such as the user changing the `snap_channel`
and wondering why the snap isn't being updated.
So the charm can alert the user to this situation
via a message and blocked status.

Fixes: #113
samuelallan72 added a commit that referenced this issue Oct 20, 2024
When a resource is used, the `snap_channel` config option is ignored.
In this case, the snap is installed directly from the resource file,
so a "channel" doesn't make sense.

If `snap_channel` is set and a resource is being used,
it may indicate a confusion situation,
such as the user changing the `snap_channel`
and wondering why the snap isn't being updated.
So the charm can alert the user to this situation
via a message and blocked status.

Fixes: #113
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant