Handle strict SSL enforce=true in GoogleCloudApigeeV1TlsInfoArgs

[rhysm-cdx]

Hello!

• Vote on this issue by adding a 👍 reaction
• If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

_inputs.py in the python apk for Apigee doesn't parse enforce=true in GoogleCloudApigeeV1TlsInfoArgs, so we cannot use this configuration in an Apigee target server managed by Pulumi.

TypeError: GoogleCloudApigeeV1TlsInfoArgs.__init__() got an unexpected keyword argument 'enforce'

https://cloud.google.com/apigee/docs/reference/apis/apigee/rest/v1/organizations.environments.targetservers#TlsInfo

Affected area/feature

Python SDK in Google native provider for pulumi / ApigeeX - environment target servers

[mjeffryes]

Hi @rhysm-cdx I would suggest you use the gcp.apigee.TargetServer resource instead of the google-native provider resources. The pulumi-gcp provider is our recommended provider for all GCP resources and google-native is not currently being updated.

[rhysm-cdx]

suggest you use the gcp.apigee.TargetServer resource instead of the google-native provider resources. The pulumi-gcp provider is our recommended provider for all GCP resources and google-native is not currently being updated.

Hi @mjeffryes Thanks for looking into the request. Would I expect the two providers to be interchangeable / backwards compatible?

[mjeffryes]

Both providers cover a similar set of resources and you can use the two side by side in the same program.

The API for a specific resource will likely be a little different on between the two providers. If you are migrating a program that is already deployed with the google-native provider to a program using GCP, you might want to consider using import to migrate the state without needing to redeploy the resources. Import Existing Cloud Infrastructure | Pulumi Docs