We’ve had scenario guides on the main documentation for some time now, but many of them are unmaintained. Three already moved to their respective collections, but we have 13 more that are just lingering in the following categories:
I’m proposing the following:
Open an issue in the collection related to the scenario guide to ask them to move the content into their collection. Let them know the stale content will be removed in Ansible 10.
Remove them all in devel branch and replace with a stub page that either points to the new location within the collection, or the collection issue we created above so readers know where to go for feedback etc. This sets us up for their removal when Ansible 10 releases.
Since we’re creating all the collection-level issues, we’ll know if the content has been moved and can update the stub with the correct pointer to the new location.
This has the benefit of removing stale documentation and hopefully convincing collection owners to take this content over and update it to match their updated collection.
Would welcome feedback on this idea before we implement it.
I agree that if it isn’t in the package, it should be removed (scenario guide). As for vmware.vmware_rest - looks like the :ref: is busted on that page. It should link to the latter above.
Yes we did and some of them got ignored. I will check to see if there is an issue already before creating a new one. I saw one that was not only ignored, but they also ignored a PR someone here did for them to move it. so
Please check if I’m right. If I am, I’d say just remove them completely.
Should I try to fix this, or do you prefer to remove the VMware REST Scenarios completely? Since the link is broken (and probably has been for some time) I tend to remove it.
@samccann Your proposal sounds reasonable, but I think these scenario guides are low hanging fruit and we can do something about them pretty easily. And then we can think what to do with the rest.
This one is strange. It doesn’t mention any collection, and two of the three modules mentioned have never been part of Ansible, while the third is part of community.general.
I would recommend to delete that guide, as it contains incorrect information.
That collection was part of Ansible, but got removed. The guide should be moved there, assuming it is still relevant. If it is no longer relevant, it should be removed.
This one belongs to oracle.oci_ansible_modules and should be part of that collection.
The Rackspace modules are currently deprecated in community.general since the Python library they use is deprecated. They will be removed in the next major community.general release. It’s probably best to simply delete that scenario guide.
My one question - on the PR that removes the guides (or adds stub pages). My initial thought was that only goes into devel, but that means for the guides @felixfontein is revamping in community.general - users won’t see that until Ansible 10. Is that okay or should we separate the ‘delete now’ guides from the ‘stub pages to new location’ guides? The latter could be backported to stable-2.16 and available in Ansible 9 on the next community.general release that picks up the new guides.
I personally think we can just keep all the changes in devel and they would become /latest/ with Ansible 10, but figured I’d ask.
I tend to keep it simple and only remove the scenario guides from devel, even if it means that the stub pages linking to the new locations won’t show up until Ansible 10.
But I’m open to split my PR into two new ones if you think it better.
for getting rid of the ones still there!