Merge lp:~suligap/canonical-identity-provider/charm-de-oops into lp:~ubuntuone-pqm-team/canonical-identity-provider/charm
Proposed by
Przemysław Suliga
Status: | Merged |
---|---|
Approved by: | Przemysław Suliga |
Approved revision: | 96 |
Merge reported by: | Otto Co-Pilot |
Merged at revision: | 99 |
Proposed branch: | lp:~suligap/canonical-identity-provider/charm-de-oops |
Merge into: | lp:~ubuntuone-pqm-team/canonical-identity-provider/charm |
Diff against target: |
118 lines (+0/-43) 5 files modified
config.yaml (+0/-16) deploy.yaml (+0/-1) playbook.yaml (+0/-2) templates/settings.py.j2 (+0/-8) unit_tests/test_templates.py (+0/-16) |
To merge this branch: | bzr merge lp:~suligap/canonical-identity-provider/charm-de-oops |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Guillermo Gonzalez | Approve | ||
Daniel Manrique (community) | Approve | ||
Review via email: mp+385254@code.launchpad.net |
Commit message
Remove OOPS config
"Remove OOPSes"
https:/
depends on this change, since the charm currently assumes that settings.OOPSES
(removed in the above MP) exists in settings_base.py
To post a comment you must log in.
+1 code-wise, also worth double-checking with GUillermo in case there's anything we need to be careful with, with removing config options from charms.
The reason is that the CI tests for SSO will try to set the configuration for both the old and new revision, and if things are not updated in the correct order, CI might fail with a version of the charm that doesn't support a specific option, and that'll leave us without a testing path and might require manual intervention.