google_privateca_certificate_authority data source should not attempt to fetch the CSR for subordinate CAs that aren't in AWAITING_USER_ACTIVATION state

[cameronhimself]

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

Terraform Version

Terraform v1.2.8

Affected Resource(s)

• google_privateca_certificate_authority data source

Terraform Configuration Files

data "google_privateca_certificate_authority" "default" {
  location = "us-east1"
  pool = "pool"
  certificate_authority_id = "subordinate-ca"
}

Debug Output

Panic Output

Expected Behavior

The data source should be retrieved with pem_csr being null.

Actual Behavior

Error when reading or editing PrivatecaCertificateAuthority "projects/{project}/locations/{location}/caPools/{pool}/certificateAuthorities/{ca}": googleapi: Error 400: Cannot perform Certificate Authority CSR retrieval, Certificate Authority is in state ENABLED.

Steps to Reproduce

1. Create a root CA and subordinate CA.
2. Activate and enable the subordinate CA.
3. Attempt to pull the subordinate CA in as a data source

Important Factoids

References

[cameronhimself]

Addressed by #12435.

[cameronhimself]

Aaaand addressed upstream by GoogleCloudPlatform/magic-modules#6496

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