After NETWAYS has already taken a leading role in the past in maintaining the Ansible Collection Icinga, contributing features and bug fixes, it’s now official:
The Ansible Collection Icinga is moving into the NETWAYS namespace (on GitHub and Ansible Galaxy).
The people involved in the repository will remain largely the same.
What Needs to Be Done?
Shortly after the repository is moved to the NETWAYS namespace, a release will also be published in the new netways namespace on Ansible Galaxy.
The versions icinga.icinga: 0.4.0 and netways.icinga: 0.4.0 will be identical—except for the namespace.
Older releases will remain available in the Icinga namespace, newer ones will be in the NETWAYS namespace.
A 1-to-1 switch to the Ansible Collection netways.icinga is thus easily possible starting with version 0.4.0.
To do this, references in existing Ansible code need to be updated to the new namespace.
But first, the new collection should be installed.
Manually via ansible-galaxy:
ansible-galaxy collection install netways.icinga:0.4.0
You possibly need to edit an entry in a requirements.yml:
collections: # Install icinga collection (OLD) # - name: icinga.icinga # version: "0.4.0" # Install icinga collection (NEW) - name: netways.icinga version: "0.4.0"
Then install with:
ansible-galaxy install -r requirements.yml
All references to the Ansible Collection icinga.icinga in your own Ansible code must be updated.
This mainly affects the use of roles in playbooks. Internal module calls used by the collection itself are already updated in netways.icinga.
Example of role usage:
- name: Install Icinga2
become: true
hosts: icinga.example.com
vars:
icinga2_constants:
NodeName: "{{ inventory_hostname }}"
ZoneName: "main"
roles:
- icinga.icinga.repos
- icinga.icinga.icinga2
Changes to:
- name: Install Icinga2
become: true
hosts: icinga.example.com
vars:
icinga2_constants:
NodeName: "{{ inventory_hostname }}"
ZoneName: "main"
roles:
- netways.icinga.repos
- netways.icinga.icinga2
The playbook keyword collections must also be updated accordingly.
collections: - - icinga.icinga + - netways.icinga
Besides these simple playbook updates, there are other areas that should be considered:
- Your own Git repositories
- requirements.yml
- CI/CD pipelines
- Your own collections and roles
- Your own Execution Environments
- Automated jobs, e.g., in AWX / Red Hat Ansible Automation Platform / Semaphore
- Job adjustments
- Execution Environment adjustments
- etc.
References to the GitHub repository in the Icinga organization will be automatically redirected by GitHub after the transfer to NETWAYS.
git@github.com:Icinga/ansible-collection-icinga.git
to
git@github.com:NETWAYS/ansible-collection-icinga.git
Changing Git clone URLs is not strictly necessary. However, for clarity, we recommend updating these references over time as well.
With this move, the Ansible Collection Icinga gains a new home while continuing the same path, backed by the same people, the same quality, and now even closer to the NETWAYS ecosystem.
We’re excited about the future of the collection and look forward to your contributions, feedback, and continued use under the new namespace.
If you have any questions or run into issues with the transition, feel free to reach out or open an issue on GitHub. Happy automating!
