You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
HI @wata727, thanks for the awesome work on this ruleset. I'm looking to help out and contribute to the project along with a few colleagues.
We spent some time digging into the code and rule generation, very cool stuff. I did have one question regarding mappings. Are they hand written? At first I assumed they were auto-generated, but it that doesn't seem to be the case.
Any guidance is appreciated.
In addition, we will likely submit a proposal for review to help with versioning as mentioned in #30 , specifically versioning against the Azure Api Spec(for rules) but also the Terraform Provider/golang sdk for mapping.
The text was updated successfully, but these errors were encountered:
Yes. Correspondence between Terraform attributes and Azure API specs is not defined anywhere, so only it is managed by hand. There is a possibility that it can be generated from static analysis of terraform-provider-azurerm's codebase, but I don't think about the challenges now.
HI @wata727, thanks for the awesome work on this ruleset. I'm looking to help out and contribute to the project along with a few colleagues.
We spent some time digging into the code and rule generation, very cool stuff. I did have one question regarding mappings. Are they hand written? At first I assumed they were auto-generated, but it that doesn't seem to be the case.
Any guidance is appreciated.
In addition, we will likely submit a proposal for review to help with versioning as mentioned in #30 , specifically versioning against the Azure Api Spec(for rules) but also the Terraform Provider/golang sdk for mapping.
The text was updated successfully, but these errors were encountered: