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

Enforce compliance to only new changes #385

Closed
danlaramay opened this issue Oct 7, 2020 · 2 comments
Closed

Enforce compliance to only new changes #385

danlaramay opened this issue Oct 7, 2020 · 2 comments
Labels
enhancement waiting for confirmation Workaround/Fix applied, waiting for confirmation

Comments

@danlaramay
Copy link

** Question : **
I was assuming that using a plan rather than the full state would allow for someone to enforce compliance on only new changes. In my recent testing I found this not to be the case. I'm hoping to use this tool to add compliance to existing environments and think it'd be nice to start enforcing compliance for new changes, while teams work on getting existing resources compliant. I didn't create a feature request because I wasn't sure if this is already possible to do with the existing tool and wanted to verify? Thanks.

@Kudbettin
Copy link
Member

@dplpd

Thanks for submitting the issue! Does the changes at #447 help?

When its actions metadata has create could be used to filter out resources that are not newly created.

@Kudbettin Kudbettin added enhancement waiting for confirmation Workaround/Fix applied, waiting for confirmation labels Jan 19, 2021
@eerkunt
Copy link
Member

eerkunt commented Mar 9, 2021

Closing the issue since we think it is fixed and there is no response so far.

Please do not hesitate to create a new one if the problem still occurs.

@eerkunt eerkunt closed this as completed Mar 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement waiting for confirmation Workaround/Fix applied, waiting for confirmation
Projects
None yet
Development

No branches or pull requests

3 participants