GCP gen-ca doesn't work anymore

[peterj]

I think the naming format for the resource has changed.

If I use the following as CA name: "projects/my-project-name/locations/us-west1/certificateAuthorities/20210809-46c-fh8" the getmesh gen-ca command fails with:

unable to issue CA, due to error: unable to create GCP certificate: rpc error: code = NotFound desc = Requested entity was not found.

It looks like a concept of caPools was introduced - here's the full resource name of the CA I created in GCP:

projects/my-project-name/locations/us-west1/caPools/istio-tetratelabs-io/certificateAuthorities/20210809-46c-fh8

However, if I try to use the above format, getmesh fails again (different error):

unable to issue CA, due to error: unable to create GCP certificate: rpc error: code = InvalidArgument desc = Malformed collection name: 'caPools/certificateAuthorities/certificates'

I am assuming this is because getmesh still uses the v1beta version of the API/protos. Perhaps we should migrate to v1 of the privateca api.