From 9012ca09af5acd09e7fb6c8456f8503c0ca876ce Mon Sep 17 00:00:00 2001 From: Trond Hindenes Date: Sat, 10 Apr 2021 00:00:42 +0200 Subject: [PATCH] Fix table formatting --- .../components-reference/supported-pubsub/setup-gcp-pubsub.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/daprdocs/content/en/reference/components-reference/supported-pubsub/setup-gcp-pubsub.md b/daprdocs/content/en/reference/components-reference/supported-pubsub/setup-gcp-pubsub.md index 01792d99e..01e4bb5df 100644 --- a/daprdocs/content/en/reference/components-reference/supported-pubsub/setup-gcp-pubsub.md +++ b/daprdocs/content/en/reference/components-reference/supported-pubsub/setup-gcp-pubsub.md @@ -58,8 +58,7 @@ The above example uses secrets as plain strings. It is recommended to use a secr | type | N | GCP credentials type. Only `service_account` is supported. Defaults to `service_account` | `service_account` | projectId | Y | GCP project id| `myproject-123` | identityProjectId | N | If the GCP pubsub project is different from the identity project, specify the identity project using this attribute | `"myproject-123"` -| privateKeyId | N | If using explicit credentials, this field should contain the `private_key_id` field from the service account json document | `"my-proviate-key"` - +| privateKeyId | N | If using explicit credentials, this field should contain the `private_key_id` field from the service account json document | `"my-private-key"` | privateKey | N | If using explicit credentials, this field should contain the `private_key` field from the service account json | `-----BEGIN PRIVATE KEY-----` | clientEmail | N | If using explicit credentials, this field should contain the `client_email` field from the service account json | `"myservice@myproject-123.iam.gserviceaccount.com"` | clientId | N | If using explicit credentials, this field should contain the `client_id` field from the service account json | `106234234234`