openstack
/
charm-nova-cloud-controller
Code Issues Proposed changes

Deprecate separate configuration options for console TLS 

Console TLS will automatically be set up when the Nova API has TLS
enabled, either through configuration (``ssl_*``) or through
certificates relation to vault.

Having multiple knobs to set up the console TLS is not really
necessary and it adds to complexity.

Change-Id: I6efb72bced8473ad52e623318a51ed976c7ac31c
Related-Bug: #1819140
This commit is contained in:
Frode Nordahl 2019-03-22 09:49:09 +01:00
parent b182ffa7f7
commit f7674cf35e
No known key found for this signature in database
GPG Key ID: 6A5D59A3BA48373F
1 changed files with 10 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
config.yaml
View File

@ -170,6 +170,10 @@ options:
type: string
default:
description: |
DEPRECATED: Please use ssl_cert configuration option or the vault
certificates relation. This configuration option will be removed
in the 19.07 charm release.
.
Used for encrypted console connections. This differs from the SSL
certificate used for API endpoints and is used for console sessions only.
Setting this value along with console-ssl-key will enable encrypted
@ -179,7 +183,12 @@ options:
console-ssl-key:
type: string
default:
description: SSL key to use with certificate specified as console-ssl-cert.
description: |
DEPRECATED: Please use ssl_key configuration option or the vault
certificates relation. This configuration option will be removed
in the 19.07 charm release.
.
SSL key to use with certificate specified as console-ssl-cert.
enable-serial-console:
type: boolean
default: false