You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create Bash variables for getmeza.sh and source them from the ENVIRONMENT;
so that administrators can override them at run-time; or use a default.
This addresses part of issues #22 and #23
This work was performed for NASA GRC-ATF by WikiWorks per NASA Contract NNC15BA02B.
The Meza repository URL is only currently used within Yaml/Ansible scripts as part of the Autodeployer functionality. It is not used to control the working sources of a controller. It is a nuance that must be better explored and documented for use cases so that any changes or enhancements reflect user expectations.
There are actually two places where the source repository for Meza is referenced in code:
In the first case, we'll provide for overrides by setting environment variables.
In the latter cases, we'll provide for overrides with variable precedence (using
-e 'foo=baz'
extra-vars of Ansible.) https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_variables.html#understanding-variable-precedenceThe text was updated successfully, but these errors were encountered: