Migrate to terraform-plugin-sdk #948
Conversation
LorbusChris
force-pushed
the
plugin-sdk
branch
from
f74269d
to
acb36e7
Compare
LorbusChris
force-pushed
the
plugin-sdk
branch
from
acb36e7
to
670c2d0
Compare
LorbusChris
force-pushed
the
plugin-sdk
branch
from
670c2d0
to
9d7fa76
Compare
|
Rebased |
LorbusChris
force-pushed
the
plugin-sdk
branch
2 times, most recently
from
58333cd
to
591de06
Compare
Also updates the null and random providers and removes the template provider which can't be used with the plugin sdk, yet, in order to make tests pass. See: hashicorp/terraform-provider-template#75
LorbusChris
force-pushed
the
plugin-sdk
branch
from
591de06
to
331c3c1
Compare
|
Rebased again. Friendly ping @bill-rich |
|
@LorbusChris thank you for the submission, we've got this prioritized and will work on it. |
|
Any progress on this @aareet ? Thanks! |
|
Let me know if there is anything that I can do to speed this up :) |
|
ping @aareet :) |
|
Hello, The provider has now migrated to the tf sdk in PR #982 . |
|
Unfortunately it looks like #982 broke the tests (providers used in tests weren't updated to versions that use the plugin-sdk, which causes type mismatches) |
|
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks! |
ghost
locked and limited conversation to collaborators
In order to make tests pass, this PR also updates the null and random
providers and removes the template provider which can't be used with the
plugin sdk, yet.
See:
hashicorp/terraform-provider-template#75