dataflow/Job Permissions
Product: Dataflow Kind: Debugging Tree
Description
This runbook investigates Dataflow permissions and recommends remediation steps.
Areas Examined:
-
Dataflow User Account Permissions: Verify that individual Dataflow users have the necessary permissions to access and manage Dataflow jobs (e.g., create,update,cancel).
-
Dataflow Service Account Permissions: Verify that the Dataflow Service Account has the required permissions to execute and manage the Dataflow jobs
-
Dataflow Worker Service Account: Verify that the Dataflow Worker Service Account has the necessary permissions for worker instances within a Dataflow job to access input and output resources during job execution.
-
Dataflow Resource Permissions: Verify that Dataflow resources (e.g., Cloud Storage buckets, BigQuery datasets) have the necessary permissions to be accessed and used by Dataflow jobs.
By ensuring that Dataflow resources have the necessary permissions, you can prevent errors and ensure that your jobs run smoothly.
Executing this runbook
gcpdiag runbook dataflow/job-permissions \
-p project_id=value \
-p principal=value \
-p worker_service_account=value \
-p cross_project_id=value
Parameters
Name | Required | Default | Type | Help |
---|---|---|---|---|
project_id |
True | None | str | The Project ID of the resource under investigation |
principal |
True | None | str | The authenticated user account email. This is the user account that is used to authenticate the user to the console or the gcloud CLI. |
worker_service_account |
True | None | str | Dataflow Worker Service Account used for Dataflow Job Creationand execution |
cross_project_id |
False | None | str | Cross Project ID, where service account is located if it is not in the same project as the Dataflow Job |
Get help on available commands
gcpdiag runbook --help