StopInstances requires Instances, causing unnecessary provider API overhead
Bug #1260171 reported by
Andrew Wilkins
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
Low
|
Andrew Wilkins |
Bug Description
The StopInstances method of environs.
Related branches
lp:~axwalk/juju-core/lp1260171-stopinstances-ids
- Juju Engineering: Pending requested
-
Diff: 1305 lines (+232/-257)38 files modifiedcontainer/interface.go (+7/-3)
container/kvm/kvm.go (+2/-2)
container/kvm/kvm_test.go (+1/-1)
container/kvm/live_test.go (+1/-1)
container/lxc/lxc.go (+2/-2)
container/lxc/lxc_test.go (+5/-5)
dependencies.tsv (+1/-1)
environs/broker.go (+3/-2)
environs/jujutest/livetests.go (+6/-6)
environs/jujutest/tests.go (+1/-1)
provider/azure/environ.go (+17/-16)
provider/azure/environ_test.go (+11/-12)
provider/common/bootstrap.go (+1/-1)
provider/common/bootstrap_test.go (+7/-7)
provider/common/destroy.go (+6/-1)
provider/common/destroy_test.go (+11/-11)
provider/common/mock_test.go (+3/-3)
provider/dummy/environs.go (+7/-7)
provider/ec2/ec2.go (+1/-5)
provider/ec2/live_test.go (+5/-5)
provider/joyent/environ_instance.go (+39/-6)
provider/joyent/instance.go (+0/-41)
provider/joyent/local_test.go (+3/-3)
provider/local/environ.go (+5/-5)
provider/maas/environ.go (+11/-25)
provider/maas/environ_whitebox_test.go (+17/-13)
provider/maas/util.go (+3/-3)
provider/maas/util_test.go (+1/-1)
provider/manual/environ.go (+1/-1)
provider/openstack/local_test.go (+8/-8)
provider/openstack/provider.go (+23/-19)
state/apiserver/client/destroy.go (+1/-22)
worker/provisioner/kvm-broker.go (+4/-4)
worker/provisioner/kvm-broker_test.go (+3/-3)
worker/provisioner/lxc-broker.go (+4/-4)
worker/provisioner/lxc-broker_test.go (+3/-3)
worker/provisioner/provisioner_task.go (+6/-2)
worker/provisioner/provisioner_test.go (+2/-2)
Changed in juju-core: | |
milestone: | none → 1.19.3 |
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.
Generally we don't use "Medium", as it is either stuff we're working on (planned work, High) or it isn't (Low).