-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
replace t_systems_mms with telekom_mms #261
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This isn't 100% according to the renaming a collection process.
As far as I understand, the new collection t_systems_mms.icinga_director
should be added to Ansible 8. t_systems_mms.icinga_director
2.0.0 would still be contained in the Ansible community package 9 and removed from 10.
Have a look at #126. It didn't work out as expected, but I think it's a good starting point.
Thanks @mariolenz, I didn't know about the docs you linked to. I hope I've done everything right, now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM at the moment, but I'll ask some people if I'm right.
Our CI is currently failing with:
Please fix the issue so that the collection complies with the repository management section of the Collection Requirements:
|
Thanks @gotmax23, I didn't spot that! @rndmh3ro It looks like you've moved and redirected https://github.com/T-Systems-MMS/ansible-collection-icinga-director to https://github.com/telekom-mms/ansible-collection-icinga-director and this causes some trouble. I think it would have been easier to keep |
But how would I then move it and also publish a telem_mms.icinga_director version 2.0.0? I don't know how to fix this whole mess. :) |
I've created #264 to ignore the tag error. The 2.0.0 release seems to have some more problems, for example the deprecation is done only in meta/runtime.yml, but not in the modules themselves. This means that the deprecation is completely invisible for Ansible 2.9, and that it will not be visible on the docsite. Also the inventory plugin hasn't been deprecated. There's also no changelog entry for 2.0.0. |
9/changelog.yaml
Outdated
deprecated_features: | ||
- The collection ``t_systems_mms.icinga_director`` has been renamed to ``telekom_mms.icinga_director``. | ||
For now both collections are included in Ansible. The content in ``t_systems_mms.icinga_director`` | ||
will be replaced with deprecated redirects to the new collection in Ansible 9.0.0, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
will be replaced with deprecated redirects to the new collection in Ansible 9.0.0, | |
have been replaced with deprecated redirects to the new collection in Ansible 9.0.0, |
9/changelog.yaml
Outdated
- The collection ``t_systems_mms.icinga_director`` has been renamed to ``telekom_mms.icinga_director``. | ||
For now both collections are included in Ansible. The content in ``t_systems_mms.icinga_director`` | ||
will be replaced with deprecated redirects to the new collection in Ansible 9.0.0, | ||
and these redirects will eventually be removed from Ansible. Please update your |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's fix a version when this will happen:
and these redirects will eventually be removed from Ansible. Please update your | |
and these redirects will be removed from Ansible 11. Please update your |
Thanks, @felixfontein. I'll try to fix these. Should I release a 2.0.1 in Galaxy for the fixes? |
@rndmh3ro that would probably be better, especially the changelog will be useful for Ansible 9.0.0 since the information will then show up in its combined changelog. |
@felixfontein, I now forked the collection from the new namespace to the old one and created the following PR: If this PR can be merged, I'll do this. Then I'll release a 2.0.1 in the old collection. Then I'll update the build-data. |
I'm really sorry, but we've just released 8.2.0. Could you please rebase your PR an move the deprecation to 8.3.0? BTW there are two suggested changes, could you please have a look at them?
@felixfontein What do you think about this, would it help? |
We renamed our company and thus the collection-namespace here: ansible/galaxy#3174 The collection now lives here: https://github.com/telekom-mms/ansible-collection-icinga-director I released a new major version 2.0.0 in the old namespace (https://galaxy.ansible.com/t_systems_mms/icinga_director) where I added the plugin-routing to the new namespace. I also deprecated the collection in the galaxy. This way I hope in Ansible 8 the old collection will stay the same while in Ansible 9 the new collection will be used. complete process for icinga_director deprecation
I rebased and updated the PR with the suggestions. |
And I also released a 2.0.1 of the old collection, hopefully doing everything right. When running a playbook with the old modules in version 2.0.1, I get:
|
CI should be fixed by #273. |
Restart CI. |
@felixfontein Since you've approved and the CI seems to be happy, I've squashed and merged. Please let me know if you think this has been a mistake. I'll undo in this case. |
No, everything is fine! Thanks everyone for getting this done! |
We renamed our company and thus the collection-namespace here: ansible/galaxy#3174
The collection now lives here: https://github.com/telekom-mms/ansible-collection-icinga-director
I released a new major version 2.0.0 in the old namespace (https://galaxy.ansible.com/t_systems_mms/icinga_director) where I added the plugin-routing to the new namespace. I also deprecated the collection in the galaxy.
This way I hope in Ansible 8 the old collection will stay the same while in Ansible 9 the new collection will be used.