Ansible Collection for Red Hat Application Services

• Python version 3.9 or higher. Installation can be found here.
• Ansible must be installed on the machine using a version of 2.9 or greater. Installation guides for Ansible can be found here.
• This collection requires some additional dependencies to be installed:

pip install rhoas-sdks --force-reinstall
pip install python-dotenv

• Not a prerequisite but it is highly recommended to use a Python virtual environment. This collection will work best if it is used within one. To create and activate a Python virtual environment, run the following command:

python3 -m venv rhoas
. rhoas/bin/activate

Once the prerequisites are fulfilled, installation of the RHOAS collection is as follows:

ansible-galaxy collection install rhoas.rhoas

Once the prerequisites and the RHOAS collection are installed the collection can be used as follows.

Once the collection is installed, documentation for each module can be found by running the following command:

ansible-doc rhoas.rhoas.<module_name>

For example:

ansible-doc rhoas.rhoas.create_kafka

This will output the documentation for the create_kafka module. It shows the required and optional parameters for the module, along with examples of how to use the module and the output of the module.

An example Ansible playbook which demonstrates the RHOAS modules abilities can be found here.

The playbook and all modules require an 'OFFLINE_TOKEN' to be used with for authentication with the Red Hat OpenShift Application Services API. The token can be passed in via a traditional Ansible command like this:

ansible localhost -m rhoas.rhoas.create_kafka -a 'name=unique-kafka-name billing_model=standard cloud_provider=aws plan="developer.x1" region="us-east-1" openshift_offline_token=<OFFLINE_TOKEN>'

Or passed in into the playbook as a variable:

...
  tasks:
  - name: Create kafka
    rhoas.rhoas.create_kafka:
      name: "unique-kafka-name"
      openshift_offline_token: "OFFLINE_TOKEN"
...

If the token is not passed in, the module will attempt to read it from the environment variable OFFLINE_TOKEN. This token is used to authenticate the user. The token is an OpenShift Token and can be found here

Two further environment variables are used for the collection to work. These environment variables can be placed in a .env file. They are:

• API_BASE_HOST - The base host for the API. This is the base URL for the API. For example, https://api.openshift.com
• SSO_BASE_HOST - The base host for the SSO. This is the base URL for the SSO. For example, https://sso.redhat.com/auth/realms/redhat-external

If neither of these environment variables are set, the collection will default to the URLs as noted in the examples.

The collection can be used via Ansible CLI:

ansible localhost -m rhoas.rhoas.create_kafka -a 'name=unique-kafka-name billing_model=standard cloud_provider=aws plan="developer.x1" region="us-east-1" openshift_offline_token=<OFFLINE_TOKEN>'

Or in a playbook like this:

ansible-playbook rhoas_test.yml

This playbook, if run as is, will do the following:

• Provision a Red Hat OpenShift Streams for Apache Kafka instance.
• Create a Service Account.
• Create an Access Control List (ACL) for the Service Account with some default values and bind that ACL to the Kafka instance and Service Account.
• Create two Kafka topics.
  • One with some examples of different configurations available.
  • One with default values as provided by the API.
• Update topic one's configuration.
• Delete both created topics.
• Delete the service account.
• Deprovision the Red Hat OpenShift Streams for Apache Kafka instance.

The playbook will then proceed to delete the created resources and as such, some alteration of the playbook will be required to keep the resources created.

There are tests created under tests/test_suite to test the modules in plugins/modules.

1. Config test evironment
   1. Install modules from requirements.txt file
   2. Build RHOAS Ansible collection locally from the code in this repo
   3. Install Ansible collection
2. Run Tests
   1. Set OFFLINE_TOKEN
   2. Set testing environment: prod or stage
   3. Execute tests using pytest
3. Test Results:
   • XML JUnit report
   • pytest log file

Tests can be executed locally or inside a container. Container approach is recomended:

1. Build the test image: make docker/test-image/build
2. Execute interactive shell in the test container: make docker/test-container/bash
3. Inside the test container:
   1. Prepare and configure the environment: ./config_test_env.sh
   2. Set offline token: export OFFLINE_TOKEN="ey..."
   3. Execute tests: ./run_tests.sh "stage" "junit_report.xml" "pytest.log"