So the original need was because there wasn't a way to get the resource directly for offline deployments. There is now a Download link on the web page. Does that address the original concern?
Though I can note that downloading the 'resource' for an oci-image just downloads the JSON snippet that describes where you can find the OCI digest. eg:
{"ImageName":"registry.jujucharms.com/charm/.../candid-idm-image@sha256:...","Password":"...","Username":"docker-registry"}
We'd want to make sure that whatever does get implemented for resolving this issue has the right content available for what Daniel actually was hoping that '--include-resources' would do.
So the original need was because there wasn't a way to get the resource directly for offline deployments. There is now a Download link on the web page. Does that address the original concern?
Though I can note that downloading the 'resource' for an oci-image just downloads the JSON snippet that describes where you can find the OCI digest. eg: :"registry. jujucharms. com/charm/ .../candid- idm-image@ sha256: ...","Password" :"...", "Username" :"docker- registry" }
{"ImageName"
We'd want to make sure that whatever does get implemented for resolving this issue has the right content available for what Daniel actually was hoping that '--include- resources' would do.