-
Notifications
You must be signed in to change notification settings - Fork 112
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
Start using terraform-plugin-sdk v1.0.0 #382
Conversation
Is there any procedural change or deprecation we should be aware of? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Tests pass on vCD 10.0
I have not yet noticed anything. Here's the quote from official site:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Keeping the kitchen clean, nice!
Just one question: is there a measurable difference after the change in how much the provider imports (quite hard to tell from PR itself)?
It is going down a bit: # master
$ find vendor/ | wc -l
2575
$ cat go.sum | wc -l
492
# PR branch
$ find vendor/ | wc -l
2510
$ cat go.sum | wc -l
314 |
HashiCorp recently split the provider plugin from main Terraform repo.
This PR is to start using the new plugin early in 2.6 development cycle so that it is properly tested before release.
Note. Acceptance and binary tests passed successfully on at least one version of vCD which should be sufficient to prove it didn't break functionality.