cimnine
commented
4 years ago Perhaps we could start an issue to collect rules for other cloud providers, where everyone could participate without internal knowledge of tflint.
For example, I would suggest the following rule for Azure:
_The name property of an azurerm_dns_txt_record resource should always be lower case. Azure will downcase the name automatically anyway. Yet this auto-downcase by Azure causes the Azure provider to replace the resource the next time that terraform runs, because it wants to ensure that the resource's name has 'correct casing'. But name property can't be changed, so the resource will be destroyed and then re-created. The consequence is that the resource will be re-created every time that terraform runs._
I believe that if users of tflint would start collecting such knowledge it would lower the bar for interested parties to kick-off the respective plugin, even if these people do not have intimate knowledge about all the gotchas of the respective cloud themselves already.
Because otherwise only someone with intimate knowledge of the respective cloud provider and with knowledge about go/tflint could even kick-off plugin development. No doubt, that would be ideal, but it seems to me that this would be a very high entry bar.
wata727
wyardley
brucearctor
Hi folks 👋
An experimental plugin system has been released in TFLint v0.14. This is the first step towards a "pluggable" linter for TFLint to support various Terraform providers in the future.
First, I'm going to work to cut out the AWS rules built into TFLint into a plugin. At the same time, we want to start supporting the other major clouds.
Unfortunately, I don't have much knowledge of GCP and Azure. So we are looking for a new plugin maintainer who is familiar with these clouds. If you are interested, please leave a comment. Thanks!