It turns out that we cannot run the Terraform GCP provider as a shared server like we do for the AWS and Azure providers (by invoking the plugin binary with certain command-line options). We have identified another way in which we set a cookie in the native provider's environment to keep it running as a shared server. This PR switches to this method in the SharedProvider implementation.
Description of your changes
It turns out that we cannot run the Terraform GCP provider as a shared server like we do for the AWS and Azure providers (by invoking the plugin binary with certain command-line options). We have identified another way in which we set a cookie in the native provider's environment to keep it running as a shared server. This PR switches to this method in the
SharedProvider
implementation.I have:
make reviewable
to ensure this PR is ready for review.backport release-x.y
labels to auto-backport this PR if necessary.How has this code been tested
provider-jet-aws
both locally & in-cluster with a provider package by provisioning and destroying a VPC. Related PR: https://github.com/crossplane-contrib/provider-jet-aws/pull/182provider-jet-gcp
both locally & in-cluster with a provider package by provisioning and destroying a ServiceAccount. Related PR: https://github.com/crossplane-contrib/provider-jet-gcp/pull/58provider-jet-azure
both locally & in-cluster with a provider package by importing a ResourceGroup. Related PR: https://github.com/crossplane-contrib/provider-jet-azure/pull/179