Make it easier to release charms in CI and in general
Metadata
Current evaluation
No evaluation has been recorded for this issue yet.
Issue body
### What needs to get done
I would like to be able to upload + release both charm and resources in one command, without having to deal with charm revisions and resource revisions directly.
For example:
```
charmcraft upload grafana-k8s_ubuntu-20.04-amd64.charm \
--resource grafana-image=ubuntu/grafana:9.2-22.04_beta \
--resource litestream-image=docker.io/litestream/litestream:0.4.0-beta.2 \
--release edge
```
Specifically:
- The user doesn't need to deal with `skopeo` or local image registry themselves.
- The user doesn't need to keep track of integer ids for charm/resource between multiple commands to release a charm.
### Why it needs to get done
- Currently we're relying on a github action with >20kLOC which is difficult to maintain.
- The know-how of releasing a charm is buried deep below piles of github yaml and js.
Evaluation history
No evaluation history available.