This causes apply-test.sh to get the list of puppet modules to do
integration test with from modules.env. Modules.env has been
refactored to have three lists of modules: Package modules(MODULES),
SOURCE_MODULES, and INTEGRATION_MODULES.
When PUPPET_INTEGRATION_TEST is not set, INTEGRATION_MODULES is
folded into SOURCE_MODULES.
In apply-test.sh, INTEGRATION_MODULES is sourced from modules.env
and some string/array manipulation is performed to pass each entry
to zuul-cloner.
Change-Id: I47302c5c7e8c41b985f16a05c4e9b8078ea867a3
Part of an effort to split most of puppet modules out of system-config.
https://review.openstack.org/#/c/130619/ should land before this
commit can be merged.
Change-Id: I7720ad7d2b25816c63e971112a7a733bde52b7f3
Use case: Our team would like to use install_modules.sh
in other places beyond openstack-infra/config, we would
also like to provide some control over what install_modules.sh
installs beyond what is given as defaults.
* Added a copyright notice so we can use it in other projects
* if a modules.env file is found in the same directory
as install_modules.sh then source the modules.env
* an export called MODULE_ENV_FILE can be included to
augment the name of the file from modules.env
to an alternative file name like modules.test.env.
This gives users of the script an option to provide
different modules on different test environments.
* as export to change the path from the default
directory to an alternate directory can be
specified with the export MODULE_ENV_PATH var.
The default directory is the same location as
the install_modules.sh script.
Change-Id: I0c3f9bcb3e91236ceca492426ee6105242a2c8eb
