GCP Certificate Authority Service support

[paulwilljones]

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 the issue is assigned to the "modular-magician" user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If the issue is assigned to a user, that user is claiming responsibility for the issue. If the issue is assigned to "hashibot", a community member has claimed the issue already.

Description

Added support for GCP Certificate Authority Service. Currently in beta, with apiv1beta1 support merged into google-cloud-go SDK.

New or Affected Resource(s)

• google_privateca_certificateauthority
• google_privateca_certificate

[GregoireW]

This product is beta so not sure what it is plan / done / known about those new resources. Anyway I write the result of my test here.

With provider 3.64,

• The PR on magic-modules state SUBORDINATE certificates are not working correctly, so it is not a big surprise they don't. (need to activate manually)
• If we apply a tf to create a subordonate ca, then the next time we plan, tf will try to replace the resource (destroy / re-create)
• an output of google_privateca_certificate.xxxxx.pem_certificates return an empty list (should return the certificate chain). google_privateca_certificate.xxxxx.pem_certificate (without the 's') will return the certificate correctly.

[melinath]

b/259264347

[melinath]

Closing - it looks like the requested resources have been implemented for a while now. If there are any issues or additional requests, please open a new ticket.

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.