Open christcottrell opened 1 year ago
@christcottrell - Apologies to getting to this issue late. Dapr Yaml files keep to a consistent naming convention across all of them, hence projectId and not project_id. Did you get this to work, or have you got more detailed information on the error that you are seeing?
@christcottrell Any feedback or update here?
Describe the issue
I am not able to get this to work, but I did also notice there is no "topic" field specified in the document. I am adding the topic, but I am getting this error:
error creating pubsub client: pubsub(publisher): google: could not find default credentials. See https://cloud.google.com/docs/authentication/external/set-up-adc for more information"
At first, I thought it should have been project_id and not projectId because Secrets Manager for GCP uses project_id. Suggestion is to make it consistent. I am using the same service account and credentials to connect. Is there possibly something wrong with the connector to GCP Cloud Pub Sub or am I missing something?
URL of the docs https://docs.dapr.io/reference/components-reference/supported-pubsub/setup-gcp-pubsub/
Expected content I believe topic is an attribute based on other sources I am seeing. And for consistency sake, accepting project_id to be similar with how other GCP configuration is done makes sense.
Additional context As noted above, even adding topic to the settings does not help. Below is the error I am seeing.. And I am using the same service account used for Secrets Manager that is working seems to have this auth issue.
error creating pubsub client: pubsub(publisher): google: could not find default credentials. See https://cloud.google.com/docs/authentication/external/set-up-adc for more information"
Thank you so much! Chris