Subordinate CA activation resource

[drebes]

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.

Subordinate CA activation resource

On GoogleCloudPlatform/magic-modules#5055 we fixed the creation of subordinate CAs. To continue work on supporting easier activation of those, we need a resource that can activate a subordinate CA that has been created but is still pending activation (AWAITING_USER_ACTIVATION). That signed sub CA cert is issued offline and then passed to this resource for activation.

New or Affected Resource(s)

• google_privateca_certificate_authority_activation

Potential Terraform Configuration

resource "google_privateca_certificate_authority" "sub" {
  ... 
  type = "SUBORDINATE"
}

resource "google_privateca_certificate_authority_activation" "example" {
{
  certificate_authority = google_privateca_certificate_authority.sub.id
  pem_ca_certificate = file("${path.root}/sub_ca_cert.pem")
  subordinate_config {
    pem_issuer_chain {
      pem_certificates = [
        file("${path.root}/root_ca_cert.pem"),
      ]
    }
  }  
}

References

https://cloud.google.com/certificate-authority-service/docs/reference/rest/v1/projects.locations.caPools.certificateAuthorities/activate

• Support configuring Subordinate CA with PrivateCA resources #9604

[melinath]

b/259264561

[gfxcc]

Requested feature is added via GoogleCloudPlatform/magic-modules#6161

[melinath]

👍 it looks like the PR only added the link to the issue without noting that it fixed the issue, so Github automation didn't automatically close this issue. Thanks!

[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.