3abb38ae14
Because the designate parameters will always need to be edited for a deployment, a copy of the environment must be made. However, because there were resource_registry entries in the previous enable-designate environments those relative paths would become invalid if the file was moved. Splitting the resource_registry entries from the user-configured parameters should eliminate this problem. Change-Id: I8817a36e20e7a75b340a0d6cb0abf09e57b1fd63
20 lines
1.1 KiB
YAML
20 lines
1.1 KiB
YAML
# *******************************************************************
|
|
# This file was created automatically by the sample environment
|
|
# generator. Developers should use `tox -e genconfig` to update it.
|
|
# Users are recommended to make changes to a copy of the file instead
|
|
# of the original, if any customizations are needed.
|
|
# *******************************************************************
|
|
# title: Enable Designate Service
|
|
# description: |
|
|
# EXPERIMENTAL: This service is not considered ready for production and
|
|
# should only be used for development and test purposes at this time.
|
|
#
|
|
# This environment enables the Designate services. One of the
|
|
# designate-config* environment files must also be included.
|
|
resource_registry:
|
|
OS::TripleO::Services::DesignateApi: ../docker/services/designate-api.yaml
|
|
OS::TripleO::Services::DesignateCentral: ../docker/services/designate-central.yaml
|
|
OS::TripleO::Services::DesignateMDNS: ../docker/services/designate-mdns.yaml
|
|
OS::TripleO::Services::DesignateProducer: ../docker/services/designate-producer.yaml
|
|
OS::TripleO::Services::DesignateWorker: ../docker/services/designate-worker.yaml
|