Browse Source

Rename no-tls environment

It was using a wrong name, which came by accident since it was
introduced to the sample environment generator.

Change-Id: I154af6d0b7ebf5cd339d5d06eaaf9b1ab66814b0
Related-Bug: #1796022
changes/41/607841/5
Juan Antonio Osorio Robles 4 years ago
parent
commit
3ecbf827ec
  1. 0
      environments/ssl/no-tls-endpoints-public-ip.yaml
  2. 2
      sample-env-generator/ssl.yaml
  3. 1
      tools/yaml-validate.py

0
environments/ssl/no-tls-endpoints-public.yaml → environments/ssl/no-tls-endpoints-public-ip.yaml

2
sample-env-generator/ssl.yaml

@ -452,7 +452,7 @@ environments:
ZaqarWebSocketPublic: {protocol: 'wss', port: '9000', host: 'CLOUDNAME'}
ZaqarWebSocketUIConfig: {protocol: 'wss', port: '443', host: 'CLOUDNAME'}
-
name: ssl/no-tls-endpoints-public
name: ssl/no-tls-endpoints-public-ip
title: Deploy All Endpoints without TLS and with IP addresses
description: |
Use this environment when deploying an overcloud where all the endpoints not

1
tools/yaml-validate.py

@ -51,6 +51,7 @@ envs_containing_endpoint_map = ['no-tls-endpoints-public-ip.yaml',
'tls-endpoints-public-dns.yaml',
'tls-endpoints-public-ip.yaml',
'tls-everywhere-endpoints-dns.yaml',
'no-tls-endpoints-public-ip.yaml',
'tls-endpoints-public-dns.yaml',
'tls-endpoints-public-ip.yaml',
'tls-everywhere-endpoints-dns.yaml']

Loading…
Cancel
Save