Bases: object
Get the layered NamespaceRepo model.
This is where we construct the “the onion” by layering NamespaceRepo models on top of each other, starting with the DB at the bottom.
context – The RequestContext
authorization_layer – Controls whether or not we add the legacy glance.authorization and glance.policy layers.
An NamespaceRepo-like object
Get the layered MetadefObjectRepo model.
This is where we construct the “the onion” by layering MetadefObjectRepo models on top of each other, starting with the DB at the bottom.
context – The RequestContext
authorization_layer – Controls whether or not we add the legacy glance.authorization and glance.policy layers.
An MetadefObjectRepo-like object
Get the layered MetadefPropertyRepo model.
This is where we construct the “the onion” by layering MetadefPropertyRepo models on top of each other, starting with the DB at the bottom.
context – The RequestContext
authorization_layer – Controls whether or not we add the legacy glance.authorization and glance.policy layers.
An MetadefPropertyRepo-like object
Get the layered MetadefResourceTypeRepo model.
This is where we construct the “the onion” by layering MetadefResourceTypeRepo models on top of each other, starting with the DB at the bottom.
context – The RequestContext
authorization_layer – Controls whether or not we add the legacy glance.authorization and glance.policy layers.
An MetadefResourceTypeRepo-like object
Get the layered MetadefTagRepo model.
This is where we construct the “the onion” by layering MetadefTagRepo models on top of each other, starting with the DB at the bottom.
context – The RequestContext
authorization_layer – Controls whether or not we add the legacy glance.authorization and glance.policy layers.
An MetadefTagRepo-like object
Get the layered ImageRepo model.
This is where we construct the “the onion” by layering ImageRepo models on top of each other, starting with the DB at the bottom.
NB: Code that has implemented policy checks fully above this layer should pass authorization_layer=False to ensure that no conflicts with old checks happen. Legacy code should continue passing True until legacy checks are no longer needed.
context – The RequestContext
authorization_layer – Controls whether or not we add the legacy glance.authorization and glance.policy layers.
An ImageRepo-like object
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.