We are renaming the Checkmk Ansible Collection

Global Community
, ,
1

Hey everyone! :wave:

This is more of a heads-up than an announcement.
We are in the process of renaming our Checkmk Ansible Collection, following the company rebranding.
While that will not include any functional changes to the collection, it is still not a trivial thing to do.
We are working towards this and are preparing as much as we can, so the transition will be as smooth as possible. However, there might be some frictions and hiccups, but we are positive it will all go well after all.

We will keep you posted in this thread about the progress and everything you need to know.
So stay tuned! :mag_right:

1 Like
2

We just started the renaming process. Stay tuned and keep your fingers crossed. :crossed_fingers:

3

The collection is now available under the new name here: Ansible Galaxy
We are still in the process of cleaning up and there might some hiccups, but the heavy lifting is done. :muscle:
If you find anything peculiar, do let us know here!
Again, we will keep you posted here. :newspaper:

4

The transition to the “new collection” is rather easy, and you have several options:

  1. You can stay on the old collection version 0.23.0 for as long as you need, nothing will break.
  2. When upgrading the old collection to 1.0.0, it will pull in the new collection as a dependency and redirect module calls. However, at this point you can still use the old FQCNs.
  3. If you install the new collection checkmk.general version 2.0.0, you need to adapt your FQCNs, so the new collection is actually used. You should also remove the old collection, so there are no mix-ups.
  4. If you start a project from scratch, start with checkmk.general directly.

Again, if you find anything, that is not working, do let us know here, so we can look into it. :microscope:

4 Likes