Don't allow legacy and native flask to share paths
When a path-prefix is moved to flask native dispatching, no longer
allow that path prefix to be registered with the legacy dispatch
middleware. This will ensure the entire Keystone path is moved
and prevent bad behavior due to both dispatchers needing ot handle
a URL.
Reviewed: https:/ /review. openstack. org/582449 /git.openstack. org/cgit/ openstack/ keystone/ commit/ ?id=0d6b427fcc7 f6b9b2a06bdd9a7 af37064e7ddd51
Committed: https:/
Submitter: Zuul
Branch: master
commit 0d6b427fcc7f6b9 b2a06bdd9a7af37 064e7ddd51
Author: Morgan Fainberg <email address hidden>
Date: Thu Jul 12 16:41:10 2018 -0700
Don't allow legacy and native flask to share paths
When a path-prefix is moved to flask native dispatching, no longer
allow that path prefix to be registered with the legacy dispatch
middleware. This will ensure the entire Keystone path is moved
and prevent bad behavior due to both dispatchers needing ot handle
a URL.
Change-Id: Ice800abf80a725 349d6450b742a2c 48238e11e6e
Partial-Bug: #1776504