Juju uses hard-coded regions
Bug #1319474 reported by
Ben Howard
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
Medium
|
Andrew Wilkins |
Bug Description
Juju currently uses hard-code "ec2.<region>
affects: | juju → juju-core |
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → Medium |
tags: | added: ec2-provider |
Changed in juju-core: | |
milestone: | none → 1.21-alpha1 |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
milestone: | 1.21-alpha1 → next-stable |
Changed in juju-core: | |
milestone: | next-stable → 1.21-alpha1 |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Simple streams describes the region to EC2 endpoint mapping, but not S3 or any others. Ian has suggested that some cloud-metadata simple streams is being developed, so we will use that when it is ready. In the mean time, we'll add another hard-coded region in goamz.