Disable invalid-name warning in run_rego #803
Open
+1
−1
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.
🗣 Description
Disable the
invalid-name
Pylint warning in run_rego.py💭 Motivation and context
A line in run_rego.py that hasn't been modified in almost a year suddenly has started causing issues for Pylint. Likely because Pylint released a new version 2 days ago. https://github.com/pylint-dev/pylint/releases/tag/v4.0.0
The guilty line is:
Pylint is mad because it's uppercase not snake case (
opa_exe
). However, it's acting like a constant so upper case is appropriate.🧪 Testing
Manually ran
pylint -d R0913,R0914,R0915,R1702,W0718,W0719,R0801 .\scubagoggles --recursive=y
✅ Pre-approval checklist
✅ Pre-merge Checklist
Squash and merge
button.✅ Post-merge Checklist