@ -513,63 +513,13 @@ This role has no dependencies on other roles, but it has dependencies on:
- Ansible (at least version 2.4)
- Ansible (at least version 2.4)
- JMESPath
- JMESPath
- Jinja (at least version 2.8)
- Jinja (at least version 2.8)
- 3scale API Management 2.3
## Usage in Ansible Tower
## Support for AWX / Tower and Jenkins
If you want to use this role in Ansible Tower, the easiest way to do so is:
You can use this role in an AWX or Tower installation by following [this guide](support/awx/).
- to have an inventory for each of your environments (dev, test, prod, etc.)
You could also use it directly from a Jenkins pipeline by following [this guide](support/jenkins/).
- in those inventories, define a group (let's say `threescale`) containing
the 3scale Admin Portal(s) of this environment
- set all the variables that depends on the environment (`threescale_cicd_wildcard_domain`, `threescale_cicd_api_environment_name`, etc.) as
group variables
- create a playbook, committed in your GIT repository and reference it as a Project
in Tower
- in this playbook, use the `assert` module to do some surface checks and set the variables that depends on the API being provisioned (such as `threescale_cicd_private_base_url`)
- create the corresponding Job Template
A very minimalistic playbook could be:
```yaml
---
- name: Deploy an API on a 3scale instance
hosts: threescale
gather_facts: no
pre_tasks:
- assert:
that:
- "git_repo is defined"
- name: Clone the git repo containing the API Definition
If you need to customize the playbooks, the inventory or both, you can follow this guide:
- define an inventory for each of your environments (dev, test, prod, etc.)
- in those inventories, define a group (let's say `threescale`) containing
the 3scale Admin Portal(s) of this environment
- set all the variables that depends on the environment (`threescale_cicd_wildcard_domain`, `threescale_cicd_api_environment_name`, etc.) as
group variables
- create a playbook, committed in your GIT repository and reference it as a Project
in Tower
- in this playbook, use the `assert` module to do some surface checks and set the variables that depends on the API being provisioned (such as `threescale_cicd_private_base_url`)
- create the corresponding Job Template
A very minimalistic playbook could be:
```yaml
---
- name: Deploy an API on a 3scale instance
hosts: threescale
gather_facts: no
pre_tasks:
- assert:
that:
- "git_repo is defined"
- name: Clone the git repo containing the API Definition