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

audit cookbook compliance run and report should not report converge #70

Closed
mhedgpeth opened this issue Jun 27, 2016 · 3 comments
Closed
Assignees
Milestone

Comments

@mhedgpeth
Copy link
Contributor

Scenario:

We still can't run the audit cookbook in production because it reports resources that are converged, which causes us to lose the ability to know when our run is entirely idempotent.

Steps to Reproduce:

Run the audit cookbook configured to run against profiles

Expected Result:

At the end of an audit cookbook run, 0 resources should report as failed

Actual Result:

resources report as converged

Implementation

The audit cookbook is implemented incorrectly. Resources in chef are there to configure the machine, not report on that machine. This is a fundamental misuse of the chef model.

Instead a report handler should be used to both download and report on the chef run. The recipe can ensure that inspec is properly installed and that the handler is used.

I am happy to create a PR for this if you think it's the right direction for the cookbook. It is a fundamental departure from what is there now.

@mhedgpeth
Copy link
Contributor Author

This is a duplicate of #23 but it doesn't look like that got fixed.

@mhedgpeth
Copy link
Contributor Author

@chris-rock I see that this cookbook went 1.0 but is still converging resources. What is the plan for fixing this?

@arlimus arlimus added this to the 1.1.0 milestone Oct 11, 2016
@vjeffrey vjeffrey self-assigned this Oct 11, 2016
@chris-rock
Copy link
Contributor

This is done with version 2.0 of the audit cookbook

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

No branches or pull requests

5 participants