3d46c8a5d9
This change has been implemented to avoid the need to backport signficantly impactful Foreign Key dropping backports. Resource is highly relational data and it makes sense to allow the use of FKs from other subsystems to project/domains. Change-Id: Ic3831d1c7ae41fe4d406d60a013770cc1258584f
13 lines
640 B
YAML
13 lines
640 B
YAML
---
|
|
upgrade:
|
|
- |
|
|
The resource backend cannot be configured to anything but SQL if the SQL
|
|
Identity backend is being used. The resource backend must now be SQL which
|
|
allows for the use of Foreign Keys to domains/projects wherever desired.
|
|
This makes managing project relationships and such much more straight
|
|
forward. The inability to configure non-SQL resource backends has been
|
|
in Keystone since at least Ocata. This is eliminating some complexity
|
|
and preventing the need for some really ugly back-port SQL migrations
|
|
in favor of a better model. Resource is highly relational and should be
|
|
SQL based.
|