-
Notifications
You must be signed in to change notification settings - Fork 69
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
Allow use actions/config/metadata in charmcraft.yaml #1126
Conversation
be67c80
to
325b211
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wow, this is a lot! 🙂
I've done a first pass here — mostly asking questions, but there are a couple of things that should go into their own refactors.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please consider my suggestions in charmcraft/models/config.py
, but whether you implement them or not is up to you. I'm fine either way!
Thanks for all of this! That was a LOT of work!
New metadata keys can be used in charmcraft.yaml if metadata.yaml not exists. tests: fix windows incomplete escape config: convert undocumented maintainer models: fix peers specs pack: bundle does not need metadata.yaml in zip config: convert new metadata to legacy metadata when export config: allow bundle without metadata.yaml
New actions keys can be used in charmcraft.yaml if actions.yaml not exists.
config keys can be used in charmcraft.yaml if config.yaml not exists.
Use new prepare_*_yaml for tests.
DISPATCH_FILENAME, | ||
HOOKS_DIRNAME, | ||
] | ||
CHARM_FILES = frozenset( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
❤️
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The only downside is some tests are order sensitive when this changed to unordered, had to add a workaround.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I hereby reaffirm my approval! 🎉
Allow use actions/config/metadata in
charmcraft.yaml
when corresponding yaml file does not exist.Metadata in
charmcraft.yaml
also must be new keys defined in spec ST087.CRAFT-1747
CRAFT-1788
CRAFT-1789