Of course, you are perfectly right dear Mike! ![]()
However, the way this compatibility Check is implemented does not care about this naming detail. We only look at the distribution name and the version number. That works good enough for the intention.
I had to work with the collection and had to workaround two things. I left comments on github ([FEED] Support CME · Issue #65 · Checkmk/ansible-collection-checkmk.general · GitHub and https://github.com/Checkmk/ansible-collection-checkmk.general/issues/186#issuecomment-1688282693).
3 posts were split to a new topic: Can the Ansible Collection handle site updates?
A post was split to a new topic: Issues with the Ansible Collection
This thread was cleaned from the release announcements, which moved here to have a nice and tidy release announcement thread. ![]()
Some posts, which replied to a release announcement directly, might look a little dangling in here, but I am positive, that the compromise is sensible and that the context still works well enough.
This thread is retained for historic reasons. ![]()