openstack
/
charm-keystone
Code Issues Proposed changes

Fix misleading example for certificate configuration 

Change-Id: I45edd7dc14d240e56c52d74147142f30f8c592d0
Closes-Bug: #1841429
This commit is contained in:
Frode Nordahl 2019-08-30 05:01:26 +02:00
parent 47d00b72e2
commit 28711f9951
No known key found for this signature in database
GPG Key ID: 6A5D59A3BA48373F
1 changed files with 10 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
README.md
View File

@ -116,13 +116,17 @@ Example bundle usage:
charm: cs:keystone
num_units: 1
options:
ssl_ca: include-base64://path-to-base64-encoded-ca-data
ssl_cert: include-base64://path-to-base64-encoded-certificate-data
ssl_key: include-base64://path-to-base64-encoded-key-data
ssl_ca: include-base64://path-to-PEM-formatted-ca-data
ssl_cert: include-base64://path-to-PEM-formatted-certificate-data
ssl_key: include-base64://path-to-PEM-formatted-key-data
NOTE: If your certificate is signed by a Certificate Authority present in the
CA Certificate Store in operating systems used in your deployment, you do not
need to provide the `ssl_ca` configuration option.
> **Note**: If your certificate is signed by a Certificate Authority present in
the CA Certificate Store in operating systems used in your deployment, you do
not need to provide the `ssl_ca` configuration option.
> **Note**: The `include-base64` bundle keyword tells Juju to source a file and
Base64 encode it before storing it as a configuration option value. The path
can be absolute or relative to the location of the bundle file.
Network Space Support
---------------------