chore: ignore linter complaints for deprecated policy.Enforce #1350
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
(cherry picked from commit 32c3d86)
emlanctot
force-pushed
the
el/ignore_linter_on_policy_enforce
branch
from
a39da50
to
b8bf385
Compare
JarrettSpiker
approved these changes
May 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
(cherry picked from commit 32c3d86)
Description
Because of the changes made to the go-tfe policy.Enforce, we're getting linter errors on this deprecated array. We've created a ticket with the compliance team to look at how we can make this backwards compatible with older versions of TFE, in the meantime we're going to ignore these errors
Remember to:
N/A
Update the Change LogN/A
Update the DocumentationExternal links