You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for the report. This is in a way expected, though the bug is that Charmcraft is still succeeding here, as it should be providing an error.
What's happening is that with the platforms key, we no longer create an implicit parts key like we did when the bases key was defined. Charmcraft should be failing if there are no parts to use. I'm guessing that the linked version is working because Charmcraft is falling back to the bases key behaviour of an implicit part when using the as-yet-unreleased platforms-only structure.
Adding the following parts key should fix the test charm:
parts:
my-charm:
source: .
plugin: charm
So we need to address two things here:
When platforms is defined but not base, still don't create an implicit part.
After that pre-processing, fail if there aren't any parts.
Bug Description
Packing a charm leads to the artifact only having the
.yaml
files inside it, thus failing to deploy.To Reproduce
charmcraft.yaml
to be the following:Environment
Ubuntu 22.04 LTS
charmcraft.yaml
The text was updated successfully, but these errors were encountered: