-
Notifications
You must be signed in to change notification settings - Fork 124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal for improving terraform taggable resources list #374
Comments
Very interesting @lonegunmanb ! |
Glad to hear that you like this idea, I'll study the blocklisting mechanic. |
Another thought just jumped in @nimrodkor, every time a provider released a new major version, a lot of deprecated resources would be removed. If we depend on the latest schema only, I would recommend we hardcode a static taggable resource list for previous major version when a new major version has been released, and we combine these list items together so |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Please keep it open as we're waiting for go-git's upgrade. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Please keep it open, thanks. |
I found that the
azurerm
resources from the taggable resource list are not update-to-date. It's very difficult to maintain this list manually every time a new provider version has been released. I assume that we also have the same problem withaws
andgcp
resources.I have a personal repo named terraform-azurerm-schema, it runs
terraform providers schema
command and extracts resource schemas returned by Terraform provider plugin, convert the schemas into go code. With the help of this library, I can detect the missing resources by the following test (that's how I compose #373 and #371):We can access any resources by calling the generated go code. I'd like to improve
yor
by two possible ways:Now I have the schema repo for the following provider:
azurerm
time
local
random
azuread
null
tls
I can add
aws
andgcp
schema repo. All schema repos have cronjob that checks whether there's new version every 6 hours. Once a new provider version has been released, a corresponding schema tag version would be generated and published.I'd like to hear your thought @nimrodkor @gruebel
The text was updated successfully, but these errors were encountered: