-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Module listen ports facts extend output #4953
Module listen ports facts extend output #4953
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
684fc60
to
a21125c
Compare
@moonrail and @gaetan-craft could one of you give me an initial review and some feedback on my idea / thoughts.
|
ready_for_review |
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 some generic comments :) (Also still needs a changelog fragment.)
changelogs/fragments/4953-listen-ports-facts-extend-output.yaml
Outdated
Show resolved
Hide resolved
Docs Build 📝Thank you for contribution!✨ This PR has been merged and your docs changes will be incorporated when they are next published. |
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.
You probably want to update the return value documentation (RETURN
) to mention the new fields.
@PKehnel this PR contains the following merge commits: Please rebase your branch to remove these commits. |
SUMMARY
Include more infos from netstat or ss to the output.
Mainly:
As raised in #4762
ISSUE TYPE
COMPONENT NAME
listen_portcs_facts
ADDITIONAL INFORMATION
Changes:
Open topics:
first time trying to contribute to a public repo, even so the pull request is not 100% done I wanted to get some initial feedback.
is the approach I took okay or should we maybe add a parameter to listen_ports_facts to contain more information, while keeping the format of the current solution as standard.
docstring type, is there a convention for this repo, I didn't find that info
Should I rework ss to have the same setup then network
Testing:
ansible-test integration listen_ports_facts --docker centos7 -v
fails for me with Gather Factes -> unreachableansible-test integration listen_ports_facts --docker -v
uses netstat is working successfulwith the warning:
WARNING: Unable to determine context for the following test targets, they will be run on the target host: listen_ports_facts
how to run pre-commit hook for my changes?
community/general/plugins/modules/system/listen_ports_facts.py
what is the verbatim output?
@gaetan-craft maybe you give me some initial feedback?