Add support for DNS-based endpoints in google_composer_environment

[jorgemur]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
• Please do not leave +1 or me too comments, they generate extra noise for issue followers and do not help prioritize the request.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.
• If an issue is assigned to a user, that user is claiming responsibility for the issue.
• Customers working with a Google Technical Account Manager or Customer Engineer can ask them to reach out internally to expedite investigation and resolution of this issue.

Description

We need support for this new flag to be able to reach the control plane from other cloud networks. dns-based_endpoint

New or Affected Resource(s)

• google_container_cluster
• google_composer_environment

Potential Terraform Configuration

References

dns-based_endpoint sdk_version_enablement

b/377317338

[jdomeracki]

Hi, I believe this should be a high priority action item.

The configuration in scope is the recommended approach from version 1.29 onward.

Best practice: Use only the DNS-based endpoint to access your control plane for simplified configuration and a flexible and policy-based layer of security.

[rileykarson]

GKE change in https://github.com/GoogleCloudPlatform/magic-modules/pull/12195, should get merged and released soon.

Adding metadata for this to go to the composer team, since that'll persist for longer.

[rileykarson]

https://github.com/GoogleCloudPlatform/magic-modules/pull/12195 is merged and will go out on 11/11 assuming no surprises in the release process. Thanks @gontech!

As stated previously, this bug will now track just the composer updates (which I am not sure are possible yet, since I can't see the field in the API, but I could have misread it)