Fix to avoid spamming syslog with invoked messages #4353
+30
−2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tanwigeetika1618
requested review from
audgirka and
alisonlhart
and removed request for
a team
tanwigeetika1618
force-pushed
the
fix-syslog-messages
branch
from
8b9c6b0
to
fb0b9fa
Compare
tanwigeetika1618
force-pushed
the
fix-syslog-messages
branch
from
fb0b9fa
to
28938c1
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix issue #4317
Description
This PR resolves the issue where
ansible-basic.pywas unnecessarily logging invoked messages to the local syslog, leading to excessive and irrelevant logging during playbook execution.Changes
CustomAnsibleModuleinargs.pyto modify the initialization process.-Preventing the unnecessary execution of
AnsibleModule.Impact
ansible-lintand checking logs withjournalctl | grep ansible.