-
Notifications
You must be signed in to change notification settings - Fork 135
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
Doc: add example of using kubectl connection plugin #741
Doc: add example of using kubectl connection plugin #741
Conversation
Build succeeded. ✔️ ansible-galaxy-importer SUCCESS in 3m 32s |
three hyphens as the berrinign of playbook in the example lead to "unparsable-with-libyaml: expected a single document in the stream - but found another document" error in yamllint, so three hyphens is removed in examples
Build succeeded. ✔️ ansible-galaxy-importer SUCCESS in 4m 23s |
Terrific improvement of the documentation. Thanks a lot @yurnov ! I have reviewed the changes and hope this can be merged. In case there is a formal flag "reviewed by tpo" or such then I could add it if someone could point me to what the syntax is. |
Can this PR be merged and backported to the Based on Ansible Project 10, the current stable version is an Ansible 9 (which include |
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.
Just minor remarks regarding FQCN and naming playbooks
changelogs/fragments/20240601-doc-example-of-using-kubectl.yaml
Outdated
Show resolved
Hide resolved
Thanks, your comments was considered |
comment intendation aligned
Build succeeded. ✔️ ansible-galaxy-importer SUCCESS in 4m 57s |
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.
A few spelling fixes.
Also, I'm unsure where any of the docs in the /docs directory here ever show up for users. They don't show up on Galaxy or docs.ansible.com. That's a broader issue than this PR but something to investigate. My limited knowledge of Galaxy/AH says files directly in the /docs directory must be .md not rst. And docs for docs.ansible.com must be in docs/docsite/rst.
@samccann We use https://github.com/ansible-network/collection_prep to generate docs. I believe this is done solely so there are docs on GH. I assume the release pipeline has its own docs build step, but I'm not sure. The docs for this plugin do show up on https://docs.ansible.com/ansible/latest/collections/kubernetes/core/kubectl_connection.html#ansible-collections-kubernetes-core-kubectl-connection. |
Ah thanks for the clarification. I saw the files but didn't put 2+2 together and realize they were just a local copy (in GH) of the module docs. |
I'm not sure how a ansible site shown docs, but in any case, they generated from DOCUMENTATION and EXAMPLES in the Python code by the https://github.com/ansible-network/collection_prep, as mentioned in CONTRIBUTING. It looks like they are combined from the rst fragments. |
doc fragment (docs/kubernetes.core.kubectl_connection.rst) is generated by collection_prep_add_docs
Build succeeded. ✔️ ansible-galaxy-importer SUCCESS in 4m 49s |
Build succeeded. ✔️ ansible-galaxy-importer SUCCESS in 4m 08s |
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.
it seems typo
Build succeeded. ✔️ ansible-galaxy-importer SUCCESS in 3m 23s |
it is recomendation by @felixfontein to avoid changed_when: false as it may confuse users and they mayht assume that you have to use that parameter most probably no-changed-when linter rule was enforced with ansible-lint v24.6.0 released yesterday https://github.com/ansible/ansible-lint/releases/tag/v24.6.0
Build succeeded. ✔️ ansible-galaxy-importer SUCCESS in 5m 09s |
and back echo "Hello, World"
Build succeeded. ✔️ ansible-galaxy-importer SUCCESS in 3m 23s |
somehow linter started to fail on example. I considered adding So, I decided (actually, it was recommended by @felixfontein in community:ansible.com matrix channel to add rule |
Build succeeded. ✔️ ansible-galaxy-importer SUCCESS in 3m 23s |
Build succeeded (gate pipeline). ✔️ ansible-galaxy-importer SUCCESS in 5m 23s |
fb80d97
into
ansible-collections:main
Backport to stable-3: 💚 backport PR created✅ Backport PR branch: Backported as #743 🤖 @patchback |
Doc: add example of using kubectl connection plugin SUMMARY Currently documentation for collection don't include any examples of using kubenrenes.core.kubectl connection plugin and it's hard to start using that plugin. ISSUE TYPE Docs Pull Request COMPONENT NAME kubenrenes.core.kubectl connection plugin ADDITIONAL INFORMATION This PR was inspired by #288 and based on feedback on that PR and my own experience. Thanks @tpo for his try and @geerlingguy for his Ansible for DevOps book Reviewed-by: Bikouo Aubin Reviewed-by: Sandra McCann <[email protected]> Reviewed-by: Mike Graves <[email protected]> Reviewed-by: Yuriy Novostavskiy Reviewed-by: purdzan (cherry picked from commit fb80d97)
Backport to stable-5: 💚 backport PR created✅ Backport PR branch: Backported as #744 🤖 @patchback |
Doc: add example of using kubectl connection plugin SUMMARY Currently documentation for collection don't include any examples of using kubenrenes.core.kubectl connection plugin and it's hard to start using that plugin. ISSUE TYPE Docs Pull Request COMPONENT NAME kubenrenes.core.kubectl connection plugin ADDITIONAL INFORMATION This PR was inspired by #288 and based on feedback on that PR and my own experience. Thanks @tpo for his try and @geerlingguy for his Ansible for DevOps book Reviewed-by: Bikouo Aubin Reviewed-by: Sandra McCann <[email protected]> Reviewed-by: Mike Graves <[email protected]> Reviewed-by: Yuriy Novostavskiy Reviewed-by: purdzan (cherry picked from commit fb80d97)
Thanks @gravesm! |
[PR #741/fb80d973 backport][stable-3] Doc: add example of using kubectl connection plugin This is a backport of PR #741 as merged into main (fb80d97). SUMMARY Currently documentation for collection don't include any examples of using kubenrenes.core.kubectl connection plugin and it's hard to start using that plugin. ISSUE TYPE Docs Pull Request COMPONENT NAME kubenrenes.core.kubectl connection plugin ADDITIONAL INFORMATION This PR was inspired by #288 and based on feedback on that PR and my own experience. Thanks @tpo for his try and @geerlingguy for his Ansible for DevOps book Reviewed-by: Yuriy Novostavskiy Reviewed-by: Mike Graves <[email protected]>
[PR #741/fb80d973 backport][stable-5] Doc: add example of using kubectl connection plugin This is a backport of PR #741 as merged into main (fb80d97). SUMMARY Currently documentation for collection don't include any examples of using kubenrenes.core.kubectl connection plugin and it's hard to start using that plugin. ISSUE TYPE Docs Pull Request COMPONENT NAME kubenrenes.core.kubectl connection plugin ADDITIONAL INFORMATION This PR was inspired by #288 and based on feedback on that PR and my own experience. Thanks @tpo for his try and @geerlingguy for his Ansible for DevOps book Reviewed-by: Mike Graves <[email protected]>
SUMMARY
Currently documentation for collection don't include any examples of using
kubenrenes.core.kubectl
connection plugin and it's hard to start using that plugin.ISSUE TYPE
COMPONENT NAME
kubenrenes.core.kubectl
connection pluginADDITIONAL INFORMATION
This PR was inspired by #288 and based on feedback on that PR and my own experience. Thanks @tpo for his try and @geerlingguy for his Ansible for DevOps book