We can use admin_context to have access to stacks
and software configs across projects. This removes
the tenant_safe flag from rpc and db api. This is
backward compatible with older rpc clients.
We still support use of global_tenant flag for listing
stacks and software configs. However, by default
an admin(user with admin role in admin_project)
would not need that.
Change-Id: I12303dbf30fb80290f95baba0c67cdf684f5f409
Remove the serializers from heat.common.wsgi, so we break the
circular import which happens if you want to import
heat.api.aws.exceptions to do a determination based on exception
type, which is required to avoid the faultwrap exception disguise
which is not applicable to the CFN API.
Partial-Bug: #1291079
Change-Id: I7498d78f8ec6098b28fb183eaaa04aa81fced3eb
Each api and test cases use different client names. This patch
changes everything to use self.rpc_client
blueprint: oslo-messaging
Change-Id: If94fd72a36cce1863296d0f64c75815abfd22a8c
This REST API creates one new base path to manage config entities:
* /{tenant_id}/software_configs
Implements: blueprint hot-software-config-rest
Change-Id: Ia1f11adbf9377f0a730ca48afcaaaee7bc3258b6