Skip to content
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

[MAINT]: Start migration towards TF Plugin Framework #1912

Open
1 task done
o-sama opened this issue Sep 21, 2023 · 6 comments
Open
1 task done

[MAINT]: Start migration towards TF Plugin Framework #1912

o-sama opened this issue Sep 21, 2023 · 6 comments
Labels
Status: Pinned A way to keep old or long lived issues around Status: Stale Used by stalebot to clean house Type: Maintenance Any dependency, housekeeping, and clean up Issue or PR

Comments

@o-sama
Copy link
Contributor

o-sama commented Sep 21, 2023

Describe the need

I won't go into detail as to why a move towards the TF Plugin Framework is a good idea, the official docs explain it better than I can 😅.

The good thing is migrating to the framework doesn't have to happen in one go, or even quickly at all. Using the terraform-plugin-mux is a good way to do one resource at a time and make sure things are migrated smoothly and without major bugs.

I'd love to hear your thoughts on this, and if it's a go, I can get started within the next week or two with setting up the muxing and start migrating resources, probably smaller ones to start with.

SDK Version

No response

API Version

No response

Relevant log output

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@o-sama o-sama added Status: Triage This is being looked at and prioritized Type: Maintenance Any dependency, housekeeping, and clean up Issue or PR labels Sep 21, 2023
@nickfloyd
Copy link
Contributor

nickfloyd commented Sep 21, 2023

Hey @o-sama we've been chatting about this internally quite a bit! ❤️ Thank you for putting some "teeth" into it here a bit. @kfcampbell is out for the next few weeks but we'll get the teams involved together and come up with a strategy here! We'd love to get your input as well so we'll reach out once we get started working through where we want to go with this!

I'd favor making this a discussion so that we can expand it to a wider audience as well as sort out what we'd like to do and then create an issue as a follow up. Thoughts?

@nickfloyd nickfloyd added Status: Blocked Some technical or requirement is blocking the issue and removed Status: Triage This is being looked at and prioritized labels Sep 21, 2023
@o-sama
Copy link
Contributor Author

o-sama commented Sep 21, 2023

@nickfloyd I'm happy to make it a discussion, the more eyes on it the better! Also feel free to reach out whenever anything is needed on my end, always happy to help 🙂

@kfcampbell
Copy link
Member

@o-sama if you'd like to start a PR that migrates one resource over or perhaps you'd like to continue #1780, that would be very much appreciated!

@o-sama
Copy link
Contributor Author

o-sama commented Oct 22, 2023

Sounds good to me, I'll take a look at the PR and also look into migrating a resource to the framework, if it isn't a lot of extra work to move towards the framework it's probably better since that'll be more future-proof.

Copy link

👋 Hey Friends, this issue has been automatically marked as stale because it has no recent activity. It will be closed if no further activity occurs. Please add the Status: Pinned label if you feel that this issue needs to remain open/active. Thank you for your contributions and help in keeping things tidy!

@github-actions github-actions bot added the Status: Stale Used by stalebot to clean house label Jul 19, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 26, 2024
@felixlut
Copy link
Contributor

felixlut commented Jul 29, 2024

As discussed in this thread, this very much still is something that should be considered!

@kfcampbell kfcampbell reopened this Jul 29, 2024
@kfcampbell kfcampbell added Status: Pinned A way to keep old or long lived issues around and removed Status: Blocked Some technical or requirement is blocking the issue labels Jul 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Pinned A way to keep old or long lived issues around Status: Stale Used by stalebot to clean house Type: Maintenance Any dependency, housekeeping, and clean up Issue or PR
Projects
None yet
Development

No branches or pull requests

4 participants