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