-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
linter: add rule to discourage data source referencing resource Read #18821
Conversation
a988114
to
a0f9e5f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me once all the fixes are in. 🚀
.semgrep.yml
Outdated
- aws/data_source_aws_*.go | ||
patterns: | ||
- pattern: $RESOURCE_READ | ||
- pattern-inside: func $FUNCNAME(...) error { ... } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will need to be updated for diag.Diagnostics
(or a separate rule created) to support context-aware functions
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ahh true! would it be too generalized of a rule if i replace error
with something like $RETURNTYPE
instead?
..welp...didn't realize what branch i was on..will fix this up |
558573f
to
5d44679
Compare
f25fa67
to
a4436a9
Compare
a4436a9
to
4200ec3
Compare
This has been released in version 3.37.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template for triage. Thanks! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Community Note
Preceded by #18838, #18842, #18844, #18846, and #18848
Closes #18819
Output from running
semgrep
(currently):