Closed mdlinville closed 2 weeks ago
Name | Link |
---|---|
Latest commit | 15f26b67de4aefefedc2cef2892824a0a4a724e5 |
Latest deploy log | https://app.netlify.com/sites/cockroachdb-interactivetutorials-docs/deploys/672a3f20e20de60008df7b2a |
Name | Link |
---|---|
Latest commit | 15f26b67de4aefefedc2cef2892824a0a4a724e5 |
Latest deploy log | https://app.netlify.com/sites/cockroachdb-api-docs/deploys/672a3f209d67fd0008d59214 |
Name | Link |
---|---|
Latest commit | 15f26b67de4aefefedc2cef2892824a0a4a724e5 |
Latest deploy log | https://app.netlify.com/sites/cockroachdb-docs/deploys/672a3f20a3b6560008cfa2d9 |
Deploy Preview | https://deploy-preview-19070--cockroachdb-docs.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
Did we used to have docs that spelled out the service account that the customer should use?
Found it on the wayback machine 😆
I think this section will need to change to mirror what we used to have here for GCP. Namely, we need to tell the customer somewhere to use crl-kms-user-{CLUSTER_ID}@{PROJECT_ID}.iam.gserviceaccount.com
. I don't think we do that anywhere right now.
I think this section will need to change to mirror what we used to have here for GCP. Namely, we need to tell the customer somewhere to use
crl-kms-user-{CLUSTER_ID}@{PROJECT_ID}.iam.gserviceaccount.com
. I don't think we do that anywhere right now.
Done, PTAL
[DOC-11624] Put back inadvertently-removed details about getting the IAM role / service account ID for CMEK