Use DeployedSSLCertificatePath for public TLS via certmonger
authorJuan Antonio Osorio Robles <jaosorior@redhat.com>
Mon, 4 Sep 2017 11:04:28 +0000 (14:04 +0300)
committerEmilien Macchi <emilien@redhat.com>
Thu, 7 Sep 2017 03:48:34 +0000 (03:48 +0000)
commitcbcfb59e1d95de21d591d33f5c2d91197c83b0a3
treecb5de99569e35901532813f7da157dadbd179ca9
parenta1d2af3918c9aeded6668ecb75532c3d820fa18d
Use DeployedSSLCertificatePath for public TLS via certmonger

As described in the bug report, DeployedSSLCertificatePath is used by
the TLS injection script (if you decide to use that).

There is an alternative, which is to use FreeIPA to provide the
certificate for public TLS (powered by certmonger); however, it doesn't
use the same path as what folks expected. This reuses the
DeployedSSLCertificatePath parameter and uses that as a path for the
resulting PEM file, so its easier to debug.

Change-Id: If73c9599d8b94d2f02b8e4c48f4a235e0fea764d
Closes-Bug: #1714932
(cherry picked from commit f395d9eab2277061e926f7956bb3a56b0c7b1131)
puppet/services/haproxy-public-tls-certmonger.yaml