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

README.md edited online with Bitbucket

Browse Source
This commit is contained in:
Don Domingo
2019-11-21 03:12:05 +00:00
parent f8b4dca86d
commit d534a15c03
1 changed files with 18 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

26
README.md
View File

@@ -27,12 +27,11 @@ sourced as environment variables to be retrieved at runtime . See the
helper-script `bin/ansible-with-atl-env` and the corresponding helper-script `bin/ansible-with-atl-env` and the corresponding
`groups_vars/aws_node_local.yml` var-file. `groups_vars/aws_node_local.yml` var-file.
#### Overriding parameters ### Customizing your deployment
If you want to customise the playbook behaviour the simplest method is to fork To customise playbook behaviour, you can fork this repository and edit it as
this repository and add your own. However, for some one-off tasks you can also needed. However, for one-off tasks you can also override the default and
override the default and calculated settings with special values. To do this, provide calculated settings with special values. To do this, provide command-line overrides to
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
@@ -61,6 +60,14 @@ them in the `Custom command-line parameters for Ansible` field:
-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 -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
#### Parameters you can override
The following files contain many of the most common system configuration parameters
you can override for your deployment:
- `[/roles/product_install/defaults/main.yml](roles/product_install/defaults/main.yml)`
- `[/group_vars/aws_node_local.yml](group_vars/aws_node_local.yml)`
## Reporting issues ## Reporting issues
If you find any bugs in this repository, or have feature requests or use cases If you find any bugs in this repository, or have feature requests or use cases
@@ -79,11 +86,14 @@ Where possible the roles are also product-agnostic (e.g. downloads), with more
specific functionality added in later product-specific roles. specific functionality added in later product-specific roles.
Roles should be reasonably self-contained, with sensible defaults configured in Roles should be reasonably self-contained, with sensible defaults configured in
`<role>/defaults/main.yml` and overridden by the playbook at runtime. Roles may `/roles/<role>/defaults/main.yml`. Like all playbook parameters, you can override
them at runtime (see
and overridden by the playbook at runtime. Roles may
implicitly depend on variables being defined elsewhere where they cannot define implicitly depend on variables being defined elsewhere where they cannot define
them natively (e.g. the `jira_config` role depends on the `atl_cluster_node_id` them natively. For example, the `jira_config` role depends on the `atl_cluster_node_id`
var being defined; on AWS this is provided by the `aws_common` role, which var being defined; on AWS this is provided by the `aws_common` role, which
should be run first). should be run first.
### Development and testing ### Development and testing