Replies: 1 comment 2 replies
-
|
Appreciate the reference 😄 — see also Hyrum's Law We generally try to avoid this sort of configuration being implemented at the rule level in favor of annotations to simply ignore the rule altogether. This keeps the scope of the ignore minimal and its purpose clear. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
This feels a little https://xkcd.com/1172/ but v0.14.0's addition of checking for unused providers with no configuration broke CI for us because we define a big file of AWS provider definitions across accounts and regions in one place and then symlink that around so we can refer to
aws.accountname_regionfor provider aliases and not have to copy and paste the definition everywhere.This is mostly because we have a lot of cross account role assumption stuff going on which we're slowly pulling out of things and then we could more nicely symlink to a more well scoped provider setup but for now it's what we have.
Could we get a configuration option to the rule to check what things the rule should check?
I'm thinking something like this:
Beta Was this translation helpful? Give feedback.
All reactions