-
Notifications
You must be signed in to change notification settings - Fork 75
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
feat(config): support type:secret
in config.options
#1625
feat(config): support type:secret
in config.options
#1625
Conversation
type:secret
in config.options
type:secret
in config.optionstype:secret
in config.options
I (foolishly!) made the same mistake here as on the earlier PR and did the GitHub UI "update" without picking the address to associate that with. I've now signed the CLA with my personal address also, so I think if that action is re-run it should pass? |
@tonyandrewmeyer I'm not sure why it's still not liking it. If you want you can rebase and force-push; otherwise I'll check tomorrow and see what we can do. |
This makes a few related changes: 1. Extensions are applied on the rawest charmcraft.yaml data we have 2. Charms with a "bases" key (not just bundles) get a default part. 3. Always expect a dictionary for parts.
3f5b420
to
701a7b9
Compare
Thanks again @tonyandrewmeyer ! This is merged |
Since Juju 3.1, the
config.options
section ofcharmcraft.yaml
(or the olderconfig.yaml
) has supported atype
value ofsecret
(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.