Replies: 2 comments 4 replies
-
Hi @23ewrdtf here's where we are right now: As you mention, google-native is currently in preview. This means there may be breaking changes and it's expected to be less stable than other providers. It also doesn't have a regular, guaranteed release cycle or bug SLA. The pulumi-gcp provder is what we describe as a "bridged" provider because it shares implementation with Google's own terraform provider. Although it's described as "classic" in the registry - this is just indicating that it's bridged rather than native. This is a fully supported provider which we indend to maintain long-term. For choosing between the providers, I would personally recommend using the "classic" provider for most day-to-day work as it's much more stable and widely tested. There might be certain features that the preview native provider recieves quicker than the classic provider - at which point you've got the option to mix and match the providers where needed to gain access to the best of both providers. |
Beta Was this translation helpful? Give feedback.
-
Thank you @danielrbradley I guess my main concern is the long term support and not need to migrate all the infrastructure from classic to native at some point in the future. |
Beta Was this translation helpful? Give feedback.
-
What happened?
The note says:
Does it mean the Google Cloud Classic will be dropped at some point and we will have to migrate to Google Cloud Native?
Expected Behavior
GCP provider should be one or if both the differences should be fully documented.Darwin
Steps to reproduce
Docs: Google Cloud (GCP) Classic and Google Cloud Native
Output of
pulumi about
✗ pulumi about
CLI
Version 3.58.0
Go Version go1.20.1
Go Compiler gc
Host
OS darwin
Version 12.6.2
Arch arm64
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
Beta Was this translation helpful? Give feedback.
All reactions