We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
At the moment, the charm config is pretty simple. In Juju ecosystem, I would say it's common to have a charm config as snap_channel or similar to select the channel to install a snap from, as a dependency of the charm. https://github.com/canonical/grafana-agent-operator/blob/49abf15ffcde20d02961118f921c34565084a310/config.yaml
snap_channel
The expected scenario is "let's test a newer revision of the snap in this Juju model deployment".
The text was updated successfully, but these errors were encountered:
We should have this as a juju config option, defaulting to latest/stable (which is currently hardcoded).
latest/stable
Sorry, something went wrong.
No branches or pull requests
Enhancement Proposal
At the moment, the charm config is pretty simple. In Juju ecosystem, I would say it's common to have a charm config as
snap_channel
or similar to select the channel to install a snap from, as a dependency of the charm.https://github.com/canonical/grafana-agent-operator/blob/49abf15ffcde20d02961118f921c34565084a310/config.yaml
The expected scenario is "let's test a newer revision of the snap in this Juju model deployment".
The text was updated successfully, but these errors were encountered: