Fix catalog compilation when not configuring endpoint
Previously when you set $configure_endpoint to false and did not have a
keystone_endpoint resource with the same name as is defined by
neutron::keystone::auth, the catalog would not be compiled. This was
because a relationship was being established where one resource in the
relationship didn't exist. This changes this so that the relationship
involving the Keystone endpoint is only defined if $configure_endpoint
is set to true.
Change-Id: I1ee51f33ffd1bf20578cd56120ee5be8e6fa0133
Co-Authored-By: Risto Laurikainen <email address hidden>
Co-Authored-By: Gael Chamoulaud <email address hidden>
Closes-Bug: 1368686
Reviewed: https:/ /review. openstack. org/190308 /git.openstack. org/cgit/ openstack/ puppet- trove/commit/ ?id=39867dcd31c acf6882ede22fb2 5d9cd62aaf1a40
Committed: https:/
Submitter: Jenkins
Branch: master
commit 39867dcd31cacf6 882ede22fb25d9c d62aaf1a40
Author: Emilien Macchi <email address hidden>
Date: Wed Jun 10 15:24:07 2015 -0400
Fix catalog compilation when not configuring endpoint
Previously when you set $configure_endpoint to false and did not have a endpoint resource with the same name as is defined by :keystone: :auth, the catalog would not be compiled. This was
keystone_
neutron:
because a relationship was being established where one resource in the
relationship didn't exist. This changes this so that the relationship
involving the Keystone endpoint is only defined if $configure_endpoint
is set to true.
Change-Id: I1ee51f33ffd1bf 20578cd56120ee5 be8e6fa0133
Co-Authored-By: Risto Laurikainen <email address hidden>
Co-Authored-By: Gael Chamoulaud <email address hidden>
Closes-Bug: 1368686