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

Update to auditd resource to check and warn of unloaded rules #6894

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

aaronlippold
Copy link
Collaborator

  • This also helps clarify FT errors when looking for rules that have been written to disk but not loaded into memory

The challenge was that the FT errors being reported were not really clear to the end user that it couldn't find the 'rule' or 'file path of the watch file' that the resource was asking for. This usually happens when a user changes the rule but does not reload them on the sytem or restart the auditd system.

This doesn't fix the issues with FT communicating better when it can't find what its looking for ( this should be another PR) but does at least make sure the user isn't in the ' I forgot to reload case' which is pretty common.

- This also helps clarify FT errors when lookding for rules that have been written to disk but not loaded into memory

Signed-off-by: Aaron Lippold <[email protected]>
Copy link

netlify bot commented Nov 29, 2023

Deploy Preview for chef-inspec canceled.

Name Link
🔨 Latest commit d41b571
🔍 Latest deploy log https://app.netlify.com/sites/chef-inspec/deploys/656797224e49bb00086e2e53

Copy link
Contributor

Hello aaronlippold! Thanks for the pull request!

Here is what will happen next:

  1. Your PR will be reviewed by the maintainers.
  2. Possible Outcomes
    a. If everything looks good, one of them will approve it, and your PR will be merged.
    b. The maintainer may request follow-on work (e.g. code fix, linting, etc). We would encourage you to address this work in 2-3 business days to keep the conversation going and to get your contribution in sooner.
    c. Cases exist where a PR is neither aligned to Chef InSpec's product roadmap, or something the team can own or maintain long-term. In these cases, the maintainer will provide justification and close out the PR.

Thank you for contributing!

@aaronlippold
Copy link
Collaborator Author

Feel free edit, add or modify this as you see fit.

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

Successfully merging this pull request may close these issues.

None yet

2 participants