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.

Sign up for GitHub

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

Jump to bottom

Add option to retain the temporary ClusterPolicy resource files #27

Closed
brandtkeller opened this issue Sep 14, 2022 · 2 comments
Closed

Add option to retain the temporary ClusterPolicy resource files #27

brandtkeller opened this issue Sep 14, 2022 · 2 comments
Labels
invalid This doesn't seem right

Comments

@brandtkeller
Copy link
Member

As a user of the compliance-auditor tool, I want to have the ability to keep the ClusterPolicy resources that were generated from the OSCAL component definition files.

It would provide a mechanism to not only inherit the ability to validate configurations, but to then actively enforce via kyverno.

Development

Add a flag (maybe keep / k) that prevents compliance-auditor from cleaning up after itself during each loop.
@brandtkeller brandtkeller added enhancement New feature or request good first issue Good for newcomers labels Sep 14, 2022
@brandtkeller brandtkeller added invalid This doesn't seem right and removed enhancement New feature or request good first issue Good for newcomers labels Oct 29, 2022
@brandtkeller
Copy link
Member Author

Moving to the invalid option until #39 can be finalized

@brandtkeller
Copy link
Member Author

Closing in favor of implementation in #42

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
invalid This doesn't seem right
Projects
Lula and Friends
Archived in project
Milestone
No milestone
Development

No branches or pull requests
1 participant
@brandtkeller