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

feat(query): remove query lambda_function_without_tags #5036

Merged

Conversation

jycamier
Copy link
Contributor

Context

assets/queries/terraform/aws/lambda_function_without_tags triggered false positive. The default_tags of the terraform providers aren't check.

The PR #4839 already fix this issue and the query queries/terraform/aws/resource_not_using_tags do already the job to check the tags usage for all taggable ressources.

Proposed Changes

  • remove the assets/queries/terraform/aws/lambda_function_without_tags query

I submit this contribution under the Apache-2.0 license.

- already check by resource_not_using_tags
@kicsbot
Copy link
Contributor

kicsbot commented Mar 23, 2022

Scan submitted to Checkmarx

@kicsbot
Copy link
Contributor

kicsbot commented Mar 23, 2022

Logo
Checkmarx SAST - Scan Summary & Details

Cx-SAST Summary

Total of 5 vulnerabilities
High 0 High
Medium 0 Medium
Low 5 Low
Info 0 Info

Violation Summary

No policy violation found

Copy link
Contributor

@rafaela-soares rafaela-soares left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @jycamier!

Such a great observation! Thank you so much for contributing 🚀

@rafaela-soares rafaela-soares added the community Community contribution label Mar 23, 2022
@rafaela-soares rafaela-soares merged commit 2207ca6 into Checkmarx:master Mar 23, 2022
@rafaela-soares rafaela-soares added the query New query feature label Aug 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community Community contribution query New query feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants