Initial migration to Terraform Plugin Framework

[tete17]

This is the first of many resources to be migrated to the Hashicorp Plugin Framework.

I chose this one because it was the smallest file that still contained test to make sure I could prove nothing had changed.

This 3 MR does 3 things:

• Add mux to both test and the main function to be able to serve 2 provider implementation under a single logical provider
• Setup the basic infrastructure for the new provider built with the Terraform Plugin Framework
• Migrate cloudamqp_intregration_aws_eventbridge to the new provider making sure test are not broken.

Note: Review should be much simpler commit by commit

Hopefully this migration will allow us to tackle issues like #214

The error messages are fairly barebones as I haven't given them too much though feel free to suggest a full rewrite on them, I focused on making the main path work, error messages are mostly an afterthought.

[dentarg]

Do you want to rebase? Seeing you make such nice commits I'm hesitant to click the Update branch button :-)

[tbroden84]

Thanks for the contribution, very appreciated. After internal discussions and how we want to prioritize our work. Migrating to framework will be put on hold until August/September to finish our other tasks before the summer. We will definitely keep an eye of any changes here.

[tete17]

Thanks for the feedback @tbroden84

I understand the concern of merging this right away. I was just trying to fix #214 as soon as I could as it is something that affects the infra I manage for my employee.

I will continue rebasing this MR as it is required. Ping me if you would like some help in other places

[tete17]

Hi @tbroden84 & @dentarg

I just rebased the branch again, let me know if you need something from my end :)

[tbroden84]

@tete17 thanks. Expect small fixes to the provider we unfortunately still have this task on hold until later. Currently internal tasks that are higher prioritized.

[tete17]

Friendly trimestral reminder that this is still open.

No rush I know it is not priority ;)

I may start working on the migration of the resource I really want in parallel

[tbroden84]

We haven't forgot about this :)

But unfortunately still occupied with more prioritized tasks.

[tete17]

Happy 2025 :)

[tete17]

Hi @tbroden84 & @dentarg

To celebrate the one year anniversary of the MR I just rebased the branch again, let me know if you need something from my end :)

[tbroden84]

@tete17 thanks :)

Sorry for not yet prioritizing this. Will lift it up on our next internal weekly meeting.

[tbroden84]

@tete17

I discussed this with my colleagues during our last development meeting, and we all agreed to dedicate more effort to this initiative. As a first step, I’ve already created a feature branch: framework migration. I’ll update this PR to target that branch (instead of main) and merge it. From there, we can continue upgrading additional resources until the entire provider is ready to be merged into main and complete the migration.

I’ve also started updating issue #281 to track the migration progress.

[tete17]

Hi @tbroden84

Thanks for merging this.

I will be honest I am a bit confused. The whole idea of this is to be able to slowly merge this MR and do small incremental releases. Minimizing the risk of breaking people integration.

Separating this into its own branch, I suspect, in an effort to merge it all together feels unnecessary risky. You will get a ton of conflicts and I doubt renovatebot will open MR against this new branch.

I of course don't have a say on any of this so consider this my humble opinion.

Pleasure working with you guys :)

[tbroden84]

@tete17 you are right, doing the feature branch will complicate things more.
Could you please open a new pull request with the same changes?

[tete17]

Happy to do so if you like but you can also merge the branch you created into master.

Let me know

[tbroden84]

Please go ahead, then we can also give credit where credit is due :)