Perhaps we could simplify the Kubernetes charming workflow by delegating work to the charm store? If a charm specifies a resource as a URL, perhaps the charm store could download it instead of the charmer.
As a user, it’s impossible–or at least quite difficult–to inspect a charm and find its upstream location.
Ignore me. From metadata.yaml - charm-k8s-kafka - [no description]
resources: kafka-image: type: oci-image description: "Image used for kafka pod." auto-fetch: true upstream-source: rocks.canonical.com:443/wurstmeister/kafka:2.12-2.2.1
It’s important to note that the upstream-source field in metadata.yaml, while a helpful pointer for people reading the charm and trying to understand where the image came from, is not used by Juju, the charm, or any of the tooling. So it’s an informational hint only, and is also entirely optional.
