The metadata about a charm is scaterred accross different places:
metadata.yaml: Charm Metadata v2
charmcraft.yaml(this “defines” the OS that the charm runs, an important information about the charm)
- a secret
versionfile that defines the version of the charm code (not the underlying service/wrokload)
- some fields that can only be filled in CharmHub.io/charms:
Summaryagain (they are already in the
- and another bit that a Canonical Engineer has to flip manually for a charm be searchable in CharmHub
This is frustrating and confusing.
Is it possible to have CharmHub pulling the metadata from the charm? This means: having
Project Homepage and
Contact in the
metadata.yaml and the
Summary from the charm metadata.
metadata.yaml has fields for
categories. This is again confusing: why we need both? where are they used? What are the categories that I can set in my charm so it can appear in CharmHub’s filters? Charmcraft could have a linter to ensure only the “valid” categories.
The information about the license used is not available anywhere (Juju should know about Charm licenses).