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

Inconsistencies between terraform and pulumi providers (v0.50) #238

Open
simplg opened this issue Oct 2, 2024 · 0 comments
Open

Inconsistencies between terraform and pulumi providers (v0.50) #238

simplg opened this issue Oct 2, 2024 · 0 comments

Comments

@simplg
Copy link

simplg commented Oct 2, 2024

I've been trying lately to migrate some of our infrastructure managed by terraform to pulumi. When trying to do a POC, I've encountered some discrepancies between the two providers.
From what I've gathered from the version number and the way the commits are made, it seems this pulumi package is generated from (or at least based on) the ovh terraform provider. However, it seems that, while the Get endpoints do seem to match between the two providers, the creation/update endpoints aren't.

For example, the GetNetworkPrivateSubnet does seem to retrieve the same informations as the terraform ressource provider v0.50 (GatewayIP, Allocation pools, ...) but the NewNetworkPrivateSubnet doesn't allow to set either GatewayIP or Allocation pools.

I forgot to mention that I'm doing the POC in go but I've seen the same discrepancies (for network subnet) in the typescript package.

@simplg simplg changed the title Inconsistencies between terraform and pulumi providers (0.50) Inconsistencies between terraform and pulumi providers (v0.50) Oct 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant