add option to deploy *.charm via url
Bug #1943519 reported by
Leon
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
It would be nice to be able to deploy a charm via url, similar to how python's requirements.txt supports git+https://... packages:
> $ juju deploy https:/
ERROR no charm was found at "https:/
or to be able to deploy a bundle with a *.charm from url rather than from local filesystem:
tester:
charm: https:/
Changed in juju: | |
importance: | Undecided → Wishlist |
Changed in juju: | |
status: | New → Triaged |
Changed in juju: | |
assignee: | nobody → Achilleas Anagnostopoulos (achilleasa) |
Changed in juju: | |
status: | Triaged → In Progress |
Changed in juju: | |
assignee: | Achilleas Anagnostopoulos (achilleasa) → nobody |
status: | In Progress → Triaged |
To post a comment you must log in.
What is the use case for having it stored in a git repository vs publishing it as the 'edge' version from Charmhub. Certainly that is the *reason* that we have edge releases (you can publish something that isn't the default that everyone else gets).
Is it because you want to try out someone's branch of a given charm? How does this work with things like resources and refresh and updates, etc.
It isn't hard to implement if we just treat it as 'just a blob to deploy' which we happen to get from a URL that isn't file://.