Potential fix for code scanning alert no. 5: Incomplete regular expression for hostnames #417
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.
Potential fix for https://github.com/terraform-linters/tflint-ruleset-google/security/code-scanning/5
To fix the issue, the dot (
.
) in the regular expression should be escaped to ensure it matches a literal dot rather than any character. This can be done by replacing.
with\.
. Additionally, using a raw string literal (enclosed in backticks) avoids the need to double-escape the backslash, making the regular expression more readable. The corrected regular expression will be:`github\.com/terraform-linters/tflint-plugin-sdk v(.+)`
This change ensures that the regular expression matches only the intended domain
github.com
and not any other unintended strings.Suggested fixes powered by Copilot Autofix. Review carefully before merging.