Contra YAML Reference¶
For many of the primitives offered by the Contra HDSL configuration information is provided, by default, via a YAML
configuration file. By default, this file is named contra.yaml, although it is possible to use an alternate file
name when calling parseConfig().
Example YAML configuration file¶
An example of what a contra.yaml file might look like can be seen below
Note
By convention, all keys are lower-cased.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 | ---
infra:
provision:
cloud:
openstack:
network:
- atomic-e2e-jenkins-test
key_pair: ci-factory
security_group:
- default
instances:
- name: rnester-database
flavor: m1.small
image: CentOS-7-x86_64-GenericCloud-1612
floating_ip_pool: 10.8.240.0
user: centos
configure:
playbooks:
- location: playbooks/configuration/install_vim.yml
tests:
playbooks:
- location: playbooks/tests/verify_vim.yml
results:
outputTypes:
artifacts:
filesToSave:
- 'linchpin/*'
- 'resources/*'
- 'Jenkinsfile'
filesToExclude: 'inventory'
reportTypes:
email:
recipientEmail:
- john@example.org
cc_email:
- paul@example.org
- george@example.org
bcc_email:
- ringo@example.org
|
Top level YAML keys¶
You can learn more about the top level keys from the links below: