blsmith/dc-deployments-automation
1
0
Fork 0
mirror of https://bitbucket.org/atlassian/dc-deployments-automation.git synced 2025-12-14 00:43:06 -06:00
Code Issues Packages Projects Releases Wiki Activity

DCD-658: README updates from review.

Browse Source
This commit is contained in:
Steve Smith
2019-09-17 15:44:02 +10:00
parent cc3cdb3b98
commit b7c3af2461
1 changed files with 9 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
README.md
View File

@@ -30,14 +30,14 @@ helper-script `bin/ansible-with-atl-env` and the corresponding
#### Overriding parameters #### Overriding parameters
If you want to customise the playbook behaviour the simplest method is to fork If you want to customise the playbook behaviour the simplest method is to fork
this repository and add your own. However for some one-off tasks may be OK to this repository and add your own. However, for some one-off tasks you can also
override the default and calculated settings with special values. This can be override the default and calculated settings with special values. To do this,
done by providing command-line overrides to provide command-line overrides to
[ansible-playbook](https://docs.ansible.com/ansible/latest/cli/ansible-playbook.html). [ansible-playbook](https://docs.ansible.com/ansible/latest/cli/ansible-playbook.html).
The most likely use-case for this is to download a custom product distribution The most likely use-case for this is to download a custom product distribution
for testing, e.g. a Jira pre-release. If you are running `ansible-playbook` for testing (for example, a pre-release version of Jira). If you are running
directly, the command-line would look like e.g: ansible-playbook directly, the command for this would look like the following:
ansible-playbook \ ansible-playbook \
-e atl_product_download_url=http://s3.amazon.com/atlassian/jira-9.0.0-PRE-TEST.tar.gz \ -e atl_product_download_url=http://s3.amazon.com/atlassian/jira-9.0.0-PRE-TEST.tar.gz \
@@ -46,10 +46,10 @@ directly, the command-line would look like e.g:
\ \
-i inv/aws_node_local aws_jira_dc_node.yml -i inv/aws_node_local aws_jira_dc_node.yml
If you are using a CloudFormation template with places the stack details in You can also do this on a CloudFormation template where the stack details are in
`/etc/atl`, the special variable `ATL_ANSIBLE_EXTRA_PARAMS` is added to the /etc/atl. On such templates, the variable `ATL_ANSIBLE_EXTRA_PARAMS` is added
`ansible-playbook` parameters in `bin/ansible-with-alt-env`. In this case you to the `ansible-playbook` parameters in `bin/ansible-with-alt-env`. In this case
would only need to set it to: you need to set it to:
ATL_ANSIBLE_EXTRA_PARAMS="-e atl_product_download_url=http://s3.amazon.com/atlassian/jira-9.0.0-PRE-TEST.tar.gz -e atl_use_system_jdk=true -e atl_download_format=tarball" ATL_ANSIBLE_EXTRA_PARAMS="-e atl_product_download_url=http://s3.amazon.com/atlassian/jira-9.0.0-PRE-TEST.tar.gz -e atl_use_system_jdk=true -e atl_download_format=tarball"