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

fix: support type:secret in config.options #1624

Closed

Conversation

tonyandrewmeyer
Copy link
Contributor

Since Juju 3.1, the config.options section of charmcraft.yaml (or the older config.yaml) has supported a type value of secret (for user secrets). This is missing from the documentation right now, but the Juju team are working on fixing that.

This PR adds support for type: secret in config options.

@tonyandrewmeyer
Copy link
Contributor Author

cf. canonical/operator#1166 where this was raised in ops.

@tonyandrewmeyer
Copy link
Contributor Author

Argh, the CLA check failed because I carelessly did the merge in the GitHub UI and didn't associate it with my Canonical email address. Is there an easy way to fix that, like signing the CLA with my personal address also?

@benhoyt
Copy link
Contributor

benhoyt commented Apr 1, 2024

@tonyandrewmeyer Would you be able to rebase with the commit author set to your Canonical email to fix the CLA check? There also seem to be various CI failures (which I haven't looked at).

@tonyandrewmeyer
Copy link
Contributor Author

Opened a replacement PR #1625.

@tonyandrewmeyer tonyandrewmeyer deleted the config-type-secret branch April 2, 2024 01:21
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 this pull request may close these issues.

2 participants