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: Ib493021ea91d6dd131d4e506735eb611444f5fef
This commit is contained in:
parent
95519fc3a9
commit
a0c29e2420
|
@ -97,14 +97,7 @@ class ec2api::keystone::auth (
|
|||
|
||||
$real_service_name = pick($service_name, $auth_name)
|
||||
|
||||
if $configure_user_role {
|
||||
Keystone_user_role["${auth_name}@${tenant}"] ~> Anchor['ec2api::service::end']
|
||||
}
|
||||
|
||||
if $configure_endpoint {
|
||||
Keystone_endpoint["${region}/${real_service_name}::${service_type}"]
|
||||
~> Anchor['ec2api::service::end']
|
||||
}
|
||||
Keystone::Resource::Service_identity['ec2api'] -> Anchor['ec2api::service::end']
|
||||
|
||||
keystone::resource::service_identity { 'ec2api':
|
||||
configure_user => $configure_user,
|
||||
|
|
Loading…
Reference in New Issue