Skip to content
This repository has been archived by the owner on Nov 11, 2022. It is now read-only.

Using Service Account with dataflow #554

Open
seehans opened this issue Feb 28, 2017 · 2 comments
Open

Using Service Account with dataflow #554

seehans opened this issue Feb 28, 2017 · 2 comments

Comments

@seehans
Copy link

seehans commented Feb 28, 2017

I am trying to use a dataflow job with a service account.
I am using the GcpOptions flags --serviceAccountKeyfile="dataflow-service-account.p12" --serviceAccountName="dataflow"

I am getting following error:
Unable to verify that GCS bucket exists.com.google.cloud.dataflow.sdk.util.DataflowPathValidator.verifyPathIsAccessible(DataflowPathValidator.java:84)
com.google.cloud.dataflow.sdk.util.DataflowPathValidator.validateOutputFilePrefixSupported(DataflowPathValidator.java:63)
com.google.cloud.dataflow.sdk.runners.DataflowPipelineRunner.fromOptions(DataflowPipelineRunner.java:274)

I would like to use service acoount credentials against application default credentials.

@seehans
Copy link
Author

seehans commented Mar 1, 2017

It works if i give following value to serviceAccountName flag:
--serviceAccountName="dataflow@my-project.gserviceaccount.com"

Documentation is misleading, we are actually giving "Service account ID" value to serviceAccountName flag and not "Service account name" .

@seehans seehans closed this as completed Mar 1, 2017
@davorbonaci
Copy link
Contributor

I'll reopen to clarify the documentation.

Thanks @seehans! Also, if you are interested, feel free to contribute a documentation fix to the Apache Beam codebase: https://github.com/apache/beam.

@davorbonaci davorbonaci reopened this Mar 1, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants