newsbot: Refactoring AWX into a Pluggable, Service-Oriented Architecture

We've got an update on how we will move to a service-oriented architecture

Our implementation plan involves several key steps:

1. Identifying Modular Services: We will start by identifying the core functionalities that can be extracted into individual plugins and/or services.
2. Creating a Communication Framework: Establish a robust communication framework to ensure seamless interaction between these services.
3. Gradual Transition: Implement the new architecture in phases to allow for continuous feedback and improvement.
4. Community Collaboration: Engage with our community throughout the process to gather feedback and ensure the new architecture meets the needs of our users.

Which will result in:

• Improved Flexibility:** Easier to implement changes and add new features.
• Enhanced Maintainability: Simplified codebase with clear service boundaries.
• Better Code Reuse: More efficient reuse of code across different projects.
• Active Community Participation: Greater opportunity for community members to contribute and shape the project.

Please join the discussion and share your perspective via the Refactoring AWX into a Pluggable, Service-Oriented Architecture forum post.

Cześć

Yesterday have a really nice troubleshouting, when discovered that in my Jenkins CI ansible condistions dosent works as expected. It quite complex one, like when: (var1 == 'something' and inventory_hostname == 'host1') or "{{ var2|bool}}"

And issue was something like:

- hosts: localhost
  gather_facts: no
  tasks:
  - set_fact:
      my_var1: "True"
      my_var2: "true,"
  - debug:
      msg: "True one"
    when: my_var1|bool
  - debug:
      msg: "True two"
    when: my_var2|bool

I had a extra comma populated from jenkins to ansible, and spent more than hour to find that issue

PLAY [localhost] ********************************************************************************************************************

TASK [set_fact] *********************************************************************************************************************
ok: [localhost]

TASK [debug] ************************************************************************************************************************
ok: [localhost] => {
    "msg": "True one"
}

TASK [debug] ************************************************************************************************************************
skipping: [localhost]

In reply to @felixfontein:matrix.org
you probably want when: (var1 == ... and inventory_ostname == 'host1') or (var2 | bool)

Please find a short example:

root@f38219e07565:/# cat /opt/playbook.yaml 
---
- hosts: localhost
  gather_facts: no
  tasks:
  - set_fact:
      var2: "true,"
  - debug:
      var: var2|bool
root@f38219e07565:/# ansible-playbook /opt/playbook.yaml 
[WARNING]: No inventory was parsed, only implicit localhost is available
[WARNING]: provided hosts list is empty, only localhost is available. Note that the implicit localhost does not match 'all'

PLAY [localhost] ********************************************************************************************************************

TASK [set_fact] *********************************************************************************************************************
ok: [localhost]

TASK [debug] ************************************************************************************************************************
ok: [localhost] => {
    "var2|bool": false
}

PLAY RECAP **************************************************************************************************************************
localhost                  : ok=2    changed=0    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0   

root@f38219e07565:/#

And in my case it was somethig like ansible-playbook -i something.yml -e var1=${VAR1} -e var2=${VAR2), playbook.yaml in Jenkins, and it lead that instead of true I had true,.