Simplify definition to ensure keystone resource creation
Use the whole resource type instead of its individual resources, to rely on interface instead of implementation of the dependent module. Change-Id: Ida8de2bfea71a3c783f4b0e4503f284e0b89aeec
This commit is contained in:
parent
95f5169393
commit
69eb2582c1
@ -121,10 +121,7 @@ class trove::keystone::auth (
|
||||
|
||||
include trove::deps
|
||||
|
||||
Keystone_user_role["${auth_name}@${tenant}"] ~> Service <| tag == 'trove-service' |>
|
||||
|
||||
Keystone_endpoint<| title == "${region}/${service_name}::${service_type}" |>
|
||||
~> Service <| tag == 'trove-service' |>
|
||||
Keystone::Resource::Service_identity['trove'] -> Anchor['trove::service::end']
|
||||
|
||||
keystone::resource::service_identity { 'trove':
|
||||
configure_user => $configure_user,
|
||||
|
Loading…
Reference in New Issue
Block a user