-
Notifications
You must be signed in to change notification settings - Fork 540
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
provider: Migrate to standalone plugin SDK v1.1.1 #558
Conversation
@radeksimko sounds great, and thank you for this PR. I'm aiming to cut a release in the next week or two. Immediately after that, I'll test this through against master, and as long as there are no surprises, I'll cut a second, separate release for this alone. |
@radeksimko alright! I just cut a release and I'm ready to get started on doing this one on its own. A couple of questions:
|
1f219c5
to
7025063
Compare
I think the convention so far was for providers to cut minor release.
I'm not sure if you meant to link to a branch, but I see a branch with a merge commit. I just did a fresh rebase, so my branch in this PR should be up to date. Can you try running acceptance tests from this branch and name the failing test? I can try to look into it. |
Thanks @radeksimko . On the build currently, I'm seeing:
I'm going to hit the re-run button, but I suspect it will give the same failure. |
@tyrannosaurus-becks That looks like a vendoring issue. Did you remember to |
Oh, that is from my branch actually - sorry for the momentary confusion - I will look into it! |
7025063
to
cd2edae
Compare
@tyrannosaurus-becks I believe this is now ready - I just forgot to rewrite import paths for the new files which were brought through the rebase from master, which then brought back I reran the whole migration, PTAL |
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.
Fantastic! Much appreciated!
provider: Migrate to standalone plugin SDK v1.1.1
This is a result of
tf-sdk-migrator migrate
and makes this provider not depend on Terraform core anymore. 🎉I would recommend cutting a separate release (2.4.0) with bumped version of Terraform before merging and releasing this, just to make it easier to pinpoint potential issues related to either of these two. There should be none, but it's a good practice to keep these in separate releases.