Skip to content
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

[DOCS] "Adding Execution Nodes" should not be under "Disable IPV6" #1672

Closed
3 tasks done
kurokobo opened this issue Dec 21, 2023 · 2 comments
Closed
3 tasks done

[DOCS] "Adding Execution Nodes" should not be under "Disable IPV6" #1672

kurokobo opened this issue Dec 21, 2023 · 2 comments
Assignees

Comments

@kurokobo
Copy link
Contributor

Please confirm the following

  • I agree to follow this project's code of conduct.
  • I have checked the current issues for duplicates.
  • I understand that the AWX Operator is open source software provided for free and that I might not receive a timely response.

Bug Summary

The documentation "Adding Execution Nodes" is under "Disable IPv6" section. This is completely different topic from IPv6-thing.

https://ansible.readthedocs.io/projects/awx-operator/en/latest/user-guide/advanced-configuration/disable-ipv6.html

AWX Operator version

latest

AWX version

N/A

Kubernetes platform

kubernetes

Kubernetes/Platform version

N/A

Modifications

no

Steps to reproduce

See the docs: https://ansible.readthedocs.io/projects/awx-operator/en/latest/user-guide/advanced-configuration/disable-ipv6.html

Expected results

"Adding Execution Nodes" should be placed as an independent page.

Actual results

"Adding Execution Nodes" is placed under "Disable IPV6"

Additional information

I don't know where "Adding Execution Nodes" should be placed, but it would be better to place it as an independent page under "Advanced Configuration" or "User Guide".

Operator Logs

No response

@jessicamack
Copy link
Member

Hello @kurokobo, thank you for catching this. You're right and an independent page under "Advanced Configuration" is fine.

@tvo318
Copy link
Member

tvo318 commented Jan 15, 2024

See also PR #1684

@tvo318 tvo318 closed this as completed Jan 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants