I’ve been building an open-source project that explores managing IBM MQ objects as code using Ansible.
The idea is simple:
YAML → Validation → Ansible → IBM MQ
For example:
queues:
- name: APP.REQUEST
type: local
host_qmgr: QM1
max_depth: 5000
The goals are:
-
Keep MQ configuration readable
-
Store configuration in Git
-
Validate before deployment
-
Make changes repeatable and idempotent
-
Reduce manual MQSC work
-
Standardize configuration across environments
I’m intentionally trying to keep the model simple enough that an MQ administrator can understand the desired state without needing deep Ansible knowledge.
The project is open source:
I’d appreciate feedback from the Ansible community, especially around:
-
YAML model design
-
Validation approaches
-
Idempotency patterns
-
Structuring Ansible automation for enterprise middleware
If anyone has experience automating middleware platforms with Ansible, I’d be interested in hearing your thoughts.