Enable haproxy internal TLS through enable-internal-tls.yaml
authorJuan Antonio Osorio Robles <jaosorior@redhat.com>
Wed, 7 Dec 2016 07:03:18 +0000 (09:03 +0200)
committerJuan Antonio Osorio Robles <jaosorior@redhat.com>
Wed, 7 Dec 2016 07:03:18 +0000 (09:03 +0200)
For usability and to reduce the number of environments that need to be
given when enabling TLS in the internal network, it's convenient to add
the enabling of TLS in the internal front-ends for HAProxy, instead of
doing that in a separate environment file.

bp tls-via-certmonger

Change-Id: Icef0c70b4b166ce2108315d5cf0763d4e8585ae1

environments/enable-internal-tls.yaml

index c01b488..6e912fa 100644 (file)
@@ -3,5 +3,6 @@
 parameter_defaults:
   EnableInternalTLS: true
 resource_registry:
+  OS::TripleO::Services::HAProxyInternalTLS: ../puppet/services/haproxy-internal-tls-certmonger.yaml
   OS::TripleO::Services::ApacheTLS: ../puppet/services/apache-internal-tls-certmonger.yaml
   OS::TripleO::Services::MySQLTLS: ../puppet/services/database/mysql-internal-tls-certmonger.yaml