fix(query): be able to check default_tags on multiple providers #4839
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
In the query
aws/resource_not_using_tags
, the query contains the following functionThis function is only able to test if there's a single provider.
the payload
input.document.provider.aws
is a struct so all is fine.If you're using more than one provider :
input.document.provider.aws
become an array of struct in this case and the rego function isn't able to access todefault_tags
.Proposed Changes
input.document.provider.aws
as our rules is impact only aws resourcesdefault_tags
if we've more than one aws providersI submit this contribution under the Apache-2.0 license.