Skip to content

Conversation

@gundalow
Copy link
Contributor

Summary

This PR updates readthedocs.io URLs to their docs.ansible.com equivalents with proper anchor preservation.

Changes (65 URLs updated)

Technical Details

  • ✅ Anchor fragments preserved during URL transformations
  • ✅ HTTP redirects followed to final destinations
  • ✅ URL validation completed before applying changes
  • ✅ Configuration-driven URL mapping system

🤖 Generated with Claude Code

Co-Authored-By: Claude [email protected]

@ansibullbot
Copy link
Collaborator

@ansibullbot ansibullbot added WIP Work in progress callback callback plugin docs module module plugins plugin (any type) labels Nov 11, 2025
@ansibullbot
Copy link
Collaborator

The test ansible-test sanity --test validate-modules [explain] failed with 15 errors:

plugins/modules/ansible_galaxy_install.py:0:0: bad-return-value-key: Return value key '<path>' found in installed_collections should not be used for return values since it cannot be accessed with dot notation in Jinja
plugins/modules/ansible_galaxy_install.py:0:0: bad-return-value-key: Return value key '<path>' found in installed_roles should not be used for return values since it cannot be accessed with dot notation in Jinja
plugins/modules/gandi_livedns.py:0:0: bad-return-value-key: Return value key 'values' found in record should not be used for return values since it cannot be accessed with dot notation in Jinja
plugins/modules/interfaces_file.py:0:0: bad-return-value-key: Return value key 'post-up' found in ifaces -> ifaces -> eth0 should not be used for return values since it cannot be accessed with dot notation in Jinja
plugins/modules/interfaces_file.py:0:0: bad-return-value-key: Return value key 'pre-up' found in ifaces -> ifaces -> eth0 should not be used for return values since it cannot be accessed with dot notation in Jinja
plugins/modules/keycloak_realm_info.py:0:0: bad-return-value-key: Return value key 'account-service' found in realm_info should not be used for return values since it cannot be accessed with dot notation in Jinja
plugins/modules/keycloak_realm_info.py:0:0: bad-return-value-key: Return value key 'token-service' found in realm_info should not be used for return values since it cannot be accessed with dot notation in Jinja
plugins/modules/keycloak_realm_info.py:0:0: bad-return-value-key: Return value key 'tokens-not-before' found in realm_info should not be used for return values since it cannot be accessed with dot notation in Jinja
plugins/modules/keycloak_realm_keys_metadata_info.py:0:0: bad-return-value-key: Return value key 'keys' found in keys_metadata should not be used for return values since it cannot be accessed with dot notation in Jinja
plugins/modules/nosh.py:0:0: bad-return-value-key: Return value key 'Required-By' found in status should not be used for return values since it cannot be accessed with dot notation in Jinja
plugins/modules/nosh.py:0:0: bad-return-value-key: Return value key 'Stopped-By' found in status should not be used for return values since it cannot be accessed with dot notation in Jinja
plugins/modules/nosh.py:0:0: bad-return-value-key: Return value key 'Wanted-By' found in status should not be used for return values since it cannot be accessed with dot notation in Jinja
plugins/modules/omapi_host.py:0:0: bad-return-value-key: Return value key 'hardware-address' found in lease should not be used for return values since it cannot be accessed with dot notation in Jinja
plugins/modules/omapi_host.py:0:0: bad-return-value-key: Return value key 'hardware-type' found in lease should not be used for return values since it cannot be accessed with dot notation in Jinja
plugins/modules/omapi_host.py:0:0: bad-return-value-key: Return value key 'ip-address' found in lease should not be used for return values since it cannot be accessed with dot notation in Jinja

click here for bot help

@gundalow gundalow force-pushed the fix-rtd-url-migration branch from 4be2122 to 8c4e94f Compare November 11, 2025 19:33
@felixfontein felixfontein added check-before-release PR will be looked at again shortly before release and merged if possible. backport-10 Automatically create a backport for the stable-10 branch backport-11 Automatically create a backport for the stable-10 branch backport-12 Automatically create a backport for the stable-12 branch labels Nov 11, 2025
@felixfontein
Copy link
Collaborator

In case you marked this as a draft because of the failing sanity tests, these have now been fixed on main.

@gundalow
Copy link
Contributor Author

In case you marked this as a draft because of the failing sanity tests, these have now been fixed on main.

Thanks for fixing the issues. I currently have a few draft PRs open to test the bulk updates.
Originally I was limiting these changes to move from rtd to docs.ansible.com, though since I'm walking over the repo I'm getting the script to check every docs.ansible.com link is still valid.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport-10 Automatically create a backport for the stable-10 branch backport-11 Automatically create a backport for the stable-10 branch backport-12 Automatically create a backport for the stable-12 branch callback callback plugin check-before-release PR will be looked at again shortly before release and merged if possible. docs module module plugins plugin (any type) WIP Work in progress

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants