-
Notifications
You must be signed in to change notification settings - Fork 22
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
Add this to Terraform's official list of providers #5
Comments
@jcs224 yes, I would be very happy to contribute this to the terraform-providers org. I have begun working on acceptance tests, which is the primary constraint right now since all resources require acceptance tests before a provider can be accepted. I'll continue working on these now and update this issue as they progress. Adding thorough tests will be an undertaking, so I would be happy to accept any contributions in the form of tests as that would speed up this process. |
I would also really like to see this. I really wish this was an "official" provider. I know it is being worked on, just shocked it doesn't already exist. I wonder how long the digital ocean provider has been "official" |
@squat going to work on adding acceptance tests for this one, documentation needed for the terraform website is being worked on too (see this branch) |
I assume your heavily using this yourself, and it seems to be the most promising candidate for official support. I probably will early adapt, unless you have a warning for me, besides the usual "unofficial" tag. BR |
@blaggacao I use this provider for managing several Kubernetes clusters. I know of others who are doing the same, e.g. https://github.com/s-urbaniak/k8s-vultr |
Any update on this? Anything the community can help with? |
@aequasi thank you for your enthusiasm! The things that still need love are:
|
i would love to work in docs :) |
@squat Looks like @afady's blitzed the acceptance tests; #27 still needs rebasing, but anything else we can help with? I noticed it doesn't work with the upcoming terraform 0.12 release, but I'm not sure if that's a requirement for being added, or how hard it would be to fix (maybe it's just a case of claiming to support that version, and verifying tests pass). |
I guess it's more likely that this one gets added: Blog announcement: |
This looks like the most active attempt at creating a solid Vultr provider for Terraform. Would you be willing to submit a PR to hashicorp/terraform?
Here are the instructions for making the PR, including testing and documentation instructions:
https://github.com/hashicorp/terraform/blob/master/.github/CONTRIBUTING.md#new-provider
We are discussing this now:
hashicorp/terraform#2611
The text was updated successfully, but these errors were encountered: