juju export-bundle does not allow a bundle to be exported without charm revisions
Bug #1835121 reported by
Dmitrii Shcherbakov
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
Low
|
Unassigned | ||
Bug Description
In many cases when we iterate on bundles we take the latest stable charm release: for example a charm released by openstack-charmers team in lp will point to the latest stable charm release.
It would be good if export-bundle allowed applications to be exported without specific revision numbers to avoid unnecessary post-processing.
Revision history for this message
| Richard Harding (rharding) wrote | #1 |
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Undecided → Wishlist |
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #2 |
| Changed in juju: | |
| importance: | Wishlist → Low |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
Thanks, I'm not sure on the export-bundle having a flag for it, or the like but it's an interesting idea. I think having a developer-like plugin for something like that would be interesting. We'll keep it in mind going forward though.