Commit 448049b2 authored by Truc Nguyen's avatar Truc Nguyen

feat(registry): add BCD registry scenario variables

parent 37c457b3
......@@ -18,15 +18,17 @@ Use these examples to customize your scenario and save it with a `.yml` file ext
These are general variables used while provisioning your platform.
| Name | Mandatory | Default | Description | Sample |
|--------------------------|-----------|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------|
| bcd_provider | Y | - | Infrastructure provider. Choose between `aws`, `azure` and `static_inventory`. With `aws` and `azure` providers, BCD may create and destroy infrastructure resources of the Bonita stack. | aws |
| bcd_stack_id | Y | - | Bonita stack identifier used to group machines by stack membership. For AWS deployments the characters allowed are limited to letters, numbers and underscore. | uswest2_test |
| bcd_inventory | N | - | Ansible inventory path required when `bcd_provider` is `static_inventory`. Example static inventories are provided in the `ansible/inventory/vagrant` directory. | ansible/inventory/vagrant/1-machine/inventory |
| bonita_on_single_host | N | false | Set to `True` when all containers of the Bonita stack is deployed on a single host. | true |
| configuration | Y | - | Configuration filename used to group variables for common deployment types. The corresponding YAML file must exist in the `ansible/vars` directory. | aws_vars |
| ansible_ssh_user | N | ubuntu | SSH user used to connect to target hosts. | ubuntu |
| ansible_private_key_file | Y | - | Path to the private SSH key used to connect to target hosts. | ~/.ssh/ABC_us-west-2.pem |
| Name | Mandatory | Default | Description | Sample |
|--------------------------|-----------|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------|
| bcd_provider | Y | - | Infrastructure provider. Choose between `aws`, `azure` and `static_inventory`. With `aws` and `azure` providers, BCD may create and destroy infrastructure resources of the Bonita stack. | aws |
| bcd_stack_id | Y | - | Bonita stack identifier used to group machines by stack membership. For AWS deployments the characters allowed are limited to letters, numbers and underscore. | uswest2_test |
| bcd_inventory | N | - | Ansible inventory path required when `bcd_provider` is `static_inventory`. Example static inventories are provided in the `ansible/inventory/vagrant` directory. | ansible/inventory/vagrant/1-machine/inventory |
| bcd_registry_user | Y | - | Docker registry username to pull Bonita images from. Provided by Bonitasoft for BCD private registry. | bonitasoft+john_doe_at_acme_com |
| bcd_registry_password | Y | - | Docker registry password to pull Bonita images from. Provided by Bonitasoft for BCD private registry. | 1234567890ABCDEFGHIJKLMNOPQRSTUVWXYZ1234567890ABCDEFGHIJKLMNOPQR |
| bonita_on_single_host | N | false | Set to `True` when all containers of the Bonita stack is deployed on a single host. | true |
| configuration | Y | - | Configuration filename used to group variables for common deployment types. The corresponding YAML file must exist in the `ansible/vars` directory. | aws_vars |
| ansible_ssh_user | N | ubuntu | SSH user used to connect to target hosts. | ubuntu |
| ansible_private_key_file | Y | - | Path to the private SSH key used to connect to target hosts. | ~/.ssh/ABC_us-west-2.pem |
## AWS provider variables
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment