9fac196988
In order to cater for implementations which 'overlay' or 'wrap' OSA and use the AIO bootstrap process, the following changes are implemented: - The paths to source the configuration files and scripts are now customisable so that the role may be executed by a playbook that is not in the OSA repository. - The path of the conf.d files may be provided to the role in order to allow conf.d files to be sourced from outside the OSA repository. - The resulting file names for the user_variables and user_secrets configuration are now customisable. Change-Id: I453342c88a6768641c96e3ff174aaeec5d554845
15 lines
773 B
YAML
15 lines
773 B
YAML
---
|
|
features:
|
|
- It is now possible to customise the location of the configuration
|
|
file source for the All-In-One (AIO) bootstrap process using the
|
|
``bootstrap_host_aio_config_path`` variable.
|
|
- It is now possible to customise the location of the scripts used
|
|
in the All-In-One (AIO) boostrap process using the
|
|
``bootstrap_host_aio_script_path`` variable.
|
|
- It is now possible to customise the name of the
|
|
``user_variables.yml`` file created by the All-In-One (AIO) bootstrap
|
|
process using the ``bootstrap_host_user_variables_filename`` variable.
|
|
- It is now possible to customise the name of the
|
|
``user_secrets.yml`` file created by the All-In-One (AIO) bootstrap
|
|
process using the ``bootstrap_host_user_secrets_filename`` variable.
|