juju should ask the charm store to decide the default series for a charm
Bug #1290824 reported by
John A Meinel
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Fix Released
|
High
|
Casey Marshall | ||
| 1.18 |
Fix Released
|
High
|
Casey Marshall | ||
Bug Description
Right now the juju client always decides that charm "foo" means "cs:precise/foo". We want to enable the charm store to make that decision if the user didn't specify it to the client. So if a user does "juju deploy mysql" juju should pass that to the charm store and find out whether the best mysql is trusty or precise.
This also requires changes to the charm-store code. An initial pass could just hard-code "precise" as long as we have an API that the client can use.
Related branches
lp:~cmars/juju-core/no-default-series
- Juju Engineering: Pending requested
-
Diff: 973 lines (+343/-137)15 files modifiedcharm/charm.go (+1/-1)
charm/repo.go (+46/-9)
charm/repo_test.go (+2/-2)
charm/testing/mockstore.go (+15/-2)
charm/url.go (+100/-47)
charm/url_test.go (+88/-34)
cmd/juju/bootstrap_test.go (+2/-2)
environs/jujutest/livetests.go (+1/-1)
juju/conn_test.go (+7/-5)
state/apiserver/charms.go (+6/-4)
state/apiserver/client/client_test.go (+14/-9)
store/lpad.go (+4/-1)
store/server.go (+21/-3)
store/server_test.go (+14/-10)
testing/charm.go (+22/-7)
lp:~cmars/juju-core/resolve-cs-series
- Juju Engineering: Pending requested
-
Diff: 1614 lines (+447/-151)40 files modifiedcharm/charm.go (+5/-5)
charm/charm_test.go (+4/-4)
charm/url.go (+17/-2)
charm/url_test.go (+20/-1)
cmd/juju/addmachine.go (+2/-1)
cmd/juju/bootstrap_test.go (+33/-20)
cmd/juju/common.go (+39/-0)
cmd/juju/deploy.go (+14/-11)
cmd/juju/environment_test.go (+14/-4)
cmd/juju/publish.go (+1/-1)
cmd/juju/upgradecharm.go (+6/-11)
cmd/juju/upgradejuju_test.go (+10/-6)
cmd/plugins/juju-metadata/imagemetadata.go (+2/-2)
cmd/plugins/juju-metadata/imagemetadata_test.go (+4/-2)
environs/bootstrap/bootstrap_test.go (+16/-9)
environs/bootstrap/synctools.go (+8/-3)
environs/config/config.go (+59/-8)
environs/config/config_test.go (+7/-6)
environs/jujutest/livetests.go (+2/-2)
environs/testing/tools.go (+9/-8)
juju/apiconn_test.go (+1/-1)
juju/testing/conn.go (+15/-2)
juju/testing/instance.go (+2/-1)
provider/azure/environ_test.go (+1/-1)
provider/common/bootstrap.go (+1/-1)
provider/dummy/environs.go (+1/-1)
provider/ec2/ec2.go (+1/-1)
provider/ec2/live_test.go (+1/-1)
provider/ec2/local_test.go (+1/-1)
provider/joyent/environ.go (+1/-1)
provider/openstack/provider.go (+1/-1)
state/api/client.go (+18/-0)
state/api/params/params.go (+16/-0)
state/apiserver/client/client.go (+40/-13)
state/apiserver/client/client_test.go (+60/-5)
testing/environ.go (+3/-1)
worker/provisioner/container_initialisation_test.go (+4/-4)
worker/provisioner/kvm-broker_test.go (+3/-4)
worker/provisioner/lxc-broker_test.go (+3/-4)
worker/provisioner/provisioner_test.go (+2/-2)
Revision history for this message
| John A Meinel (jameinel) wrote | #1 |
Revision history for this message
| John A Meinel (jameinel) wrote | #2 |
| Changed in juju-core: | |
| assignee: | nobody → Casey Marshall (cmars) |
| Changed in juju-core: | |
| status: | Triaged → In Progress |
| Changed in juju-core: | |
| status: | In Progress → Fix Committed |
| Changed in juju-core: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
I don't see a separate project for charm-store, so this aspect of the change is for the juju client.
the charm-store side of it is bug #1290828