juju environment name in deployer configs shouldn't include type of environment
Bug #1324941 reported by
Tom Haddon
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ubuntu CI Engine |
Fix Released
|
High
|
Celso Providelo | ||
Bug Description
Currently the juju-deployer configs in lp:uci-engine include ci-airline-staging as the environment name. This should be changed to ci-airline, as otherwise you're going to need completely separate juju-deployer configs for production, that would have everything renamed to ci-airline-
We (webops) will separate the environments by different tenants (stagingstack-ue and prodstack-ue) so that it's clear whether you're in a staging environment or a production environment.
Related branches
lp:~cprov/uci-engine/staging-deployment-renaming
- Andy Doan (community): Approve
- PS Jenkins bot (community): Approve (continuous-integration)
-
Diff: 188 lines (+18/-18)14 files modifiedREADME (+1/-1)
TRICKS (+2/-2)
juju-deployer/branch-source-builder.yaml.tmpl (+1/-1)
juju-deployer/deploy.py (+4/-4)
juju-deployer/gatekeeper.yaml.tmpl (+1/-1)
juju-deployer/image-builder.yaml.tmpl (+1/-1)
juju-deployer/juju-gui.yaml (+1/-1)
juju-deployer/lander.yaml.tmpl (+1/-1)
juju-deployer/ppa-assigner.yaml.tmpl (+1/-1)
juju-deployer/production-only.yaml (+1/-1)
juju-deployer/relations.yaml (+1/-1)
juju-deployer/test-runner.yaml.tmpl (+1/-1)
juju-deployer/ticket-system.yaml.tmpl (+1/-1)
tests/test_rabbit.py (+1/-1)
| Changed in uci-engine: | |
| assignee: | nobody → Celso Providelo (cprov) |
| milestone: | none → uce-0 |
| Changed in uci-engine: | |
| status: | New → In Progress |
| importance: | Undecided → High |
| Changed in uci-engine: | |
| status: | In Progress → Fix Committed |
| Changed in uci-engine: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
