-
Notifications
You must be signed in to change notification settings - Fork 104
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
Add table aws_accessanalyzer_finding #1812
Comments
As part of this work, we should also deprecate the |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
Co-authored-by: sourav chakraborty <[email protected]>
References
I think you can only have 1 analyzer per region, so we could potentially use a parent hydrate with the
aws_accessanalzyer_analyzer
table.The text was updated successfully, but these errors were encountered: