Always migrate the the db for extensions instead of conditionally
Bug #1324260 reported by
Julien Vey
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Medium
|
Steve Martinelli |
Bug Description
Following the discussion here https:/
(Adding an env_var to enable keystone extensions in devstack)
Morgan Fainberg proposed that "we should _always_ migrate the db for extensions instead of conditionally. there is no reason not to have the DB structure in place (notably to ensure consistent schemas and better deployer experience in enabling an extension)."
Changed in keystone: | |
importance: | Undecided → Medium |
milestone: | none → juno-2 |
status: | New → Triaged |
Changed in keystone: | |
assignee: | nobody → Adam Young (ayoung) |
status: | Triaged → In Progress |
Changed in keystone: | |
assignee: | Adam Young (ayoung) → Steve Martinelli (stevemar) |
Changed in keystone: | |
status: | Fix Committed → Fix Released |
Changed in keystone: | |
milestone: | juno-2 → 2014.2 |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/96326 /git.openstack. org/cgit/ openstack/ keystone/ commit/ ?id=48bb31d3be1 afd0f96023041e5 29758c3056fae8
Committed: https:/
Submitter: Jenkins
Branch: master
commit 48bb31d3be1afd0 f96023041e52975 8c3056fae8
Author: Adam Young <email address hidden>
Date: Wed May 28 21:30:35 2014 -0400
Migrate default extensions
When running `keystone-manage db_sync` with no parameters, none of
the extensions are migrated.
This patch will now, by default, migrate the following extensions:
revoke
DocImpact 9b9bccc09bd6a84 3728230b25f
Co-Authored-By: Steve Martinelli <email address hidden>
Closes-Bug: 1324260
Change-Id: I4711e8670bf961