408f794e2a
At the moment we assign `heat_stack_owner` to the `admin` user in a `service` project, which leads to a completely unwanted behaviour, since `admin` user does not have any other privileges to the `service` project rather then `heat_stack_owner`. Instead we should be granting privileges to the bootstrapped project for the admin user. This fixes unclarity and potential issues users might face in horizon by switching to the `service` project, where they have no permissions. Change-Id: I95faa779bf62524fafd09576aa7ae27de029bb57 |
||
|---|---|---|
| .. | ||
| heat_db_sync.yml | ||
| heat_install.yml | ||
| heat_post_install.yml | ||
| heat_pre_install.yml | ||
| heat_service_setup.yml | ||
| main.yml | ||