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: I21e05882b2685d8d312f4d6cc516ebcaf2ba6677
This commit is contained in:
parent
d7804328ab
commit
12a5b23668
|
@ -96,12 +96,7 @@ class barbican::keystone::auth (
|
|||
|
||||
include barbican::deps
|
||||
|
||||
Keystone_user_role<| name == "${auth_name}@${tenant}" |> -> Anchor['barbican::service::end']
|
||||
Keystone_user_role<| name == "${auth_name}@::::${system_scope}" |> -> Anchor['barbican::service::end']
|
||||
|
||||
if $configure_endpoint {
|
||||
Keystone_endpoint["${region}/${service_name}::${service_type}"] -> Anchor['barbican::service::end']
|
||||
}
|
||||
Keystone::Resource::Service_identity['barbican'] -> Anchor['barbican::service::end']
|
||||
|
||||
keystone::resource::service_identity { 'barbican':
|
||||
configure_user => $configure_user,
|
||||
|
|
Loading…
Reference in New Issue