-
Notifications
You must be signed in to change notification settings - Fork 72
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
command: charmcraft init to use charmcraft.yaml only #1149
Conversation
f9b3a0d
to
153bd08
Compare
Blocked by: |
7da3782
to
a5cf958
Compare
763a60d
to
f5c9904
Compare
7e44ed3
to
938a513
Compare
938a513
to
f4bbbbf
Compare
I think we're better off just removing the |
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.
As long as @jnsgruk and @sergiusens are on the same page as each other about removing the -legacy
templates I'm happy with that. Let's check in stand-up today and then you can merge either this as-is or without the legacy directories.
Thanks for all this work!
4d70b58
to
c367e4d
Compare
c367e4d
to
dbd8dfc
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.
👍
Use unified charmcraft.yaml by default, that included `metadata.yaml`, `actions.yaml` and `config.yaml`. Also added profiles descriptions and updated URL.
dbd8dfc
to
fc157ad
Compare
Use unified charmcraft.yaml by default, that included
metadata.yaml
,actions.yaml
andconfig.yaml
.Also added profiles descriptions and updated URL.
CRAFT-1795
CRAFT-1824