Describe the issue
Presently the GCP Pub/Sub Binding page shows that all metadata fields are required. However, I am able to successfully use this binding when providing only the fields below:
- topic
- type
- project_id
- private_key
- client_email
Note that items 2-5 also are the only fields required for GCP Secret Manager. That's why I tried this experiment. The topic field of course is specific to Pub/Sub.
Are these five fields in fact the only required ones for this binding?
URL of the docs
https://docs.dapr.io/reference/components-reference/supported-bindings/gcppubsub/
Expected content
Update the Required column to "N" for non-required fields.
Describe the issue
Presently the GCP Pub/Sub Binding page shows that all metadata fields are required. However, I am able to successfully use this binding when providing only the fields below:
Note that items 2-5 also are the only fields required for GCP Secret Manager. That's why I tried this experiment. The topic field of course is specific to Pub/Sub.
Are these five fields in fact the only required ones for this binding?
URL of the docs
https://docs.dapr.io/reference/components-reference/supported-bindings/gcppubsub/
Expected content
Update the Required column to "N" for non-required fields.