From 1efb60030200bc131245a5693754b03a8d80421e Mon Sep 17 00:00:00 2001 From: vchen7629 Date: Wed, 22 Jul 2026 11:27:27 -0700 Subject: [PATCH 1/2] docs: added section to docs/usage for google cloud storage --- docs/usage/jobkit.md | 41 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 41 insertions(+) diff --git a/docs/usage/jobkit.md b/docs/usage/jobkit.md index f1dfcb7858..930d2dcc86 100644 --- a/docs/usage/jobkit.md +++ b/docs/usage/jobkit.md @@ -49,6 +49,7 @@ The currently supported connectors are: - HTTP endpoints - S3 - Google Drive +- Google Cloud Storage ### Google Drive @@ -84,3 +85,43 @@ Step 5: Authenticate via CLI. - Run the CLI with your configuration file. - A browser window will open for authentication and gerate a token file that will be save on the configured `token_path` and reused for next runs. + +### Google Cloud Storage + +To use Google Drive as a source or target, you need to enable the API and set up credentials. + +Step 1: Enable the [Google Cloud Storage API](https://console.cloud.google.com/apis/enableflow?apiid=storage.com). + +- Go to the Google [Cloud Console](https://console.cloud.google.com/). +- Search for “Google Storage API” and enable it. + +Step 2: Create a bucket. + +- Go to Cloud Storage > Buckets > "+ Create". +- Give it a name and create it. This is your `bucket` value in the configuration file + +Step 3: Create a service account. + +- Go to IAM & Admin > Service Accounts. +- Click "+ Create service account" and create it. +- Grant it a role with bucket access: "Storage Object Admin" for source and target use ("Storage Object Viewer" for read-only sources, "Storage Object Creator" for write-only targets) + +Step 4: Create a service account key. + +- Open the service account > Keys tab. +- Click “Add key” > “Create new key” > select "JSON". +- Download the credentials JSON. + +Step 5: Edit configuration file. + +- Copy the fields from the downloaded JSON into the service_account_key block of your source or target (`project_id`, `private_key_id`, `private_key`, `client_email`, `client_id`, and the `*_uri` / `*_cert_url` fields). +- Edit `bucket` with your bucket name. +- Edit `key_prefix` with your source or target location within the bucket. It is an object-name prefix, obtained from the object path as follows: + - Folder: `gs://my-docling-bucket/source/` > prefix is `source/`. + - File: `gs://my-docling-bucket/target/output/` > prefix is target/output/. +- Edit project (optional) with your GCP `project ID` for billing / ADC. + +Step 6: Run the CLI. + +- Run the CLI with your configuration file. +- If you omit service_account_key, it falls back to Application Default Credentials, e.g. gcloud auth application-default login or Workload Identity on GKE/Cloud Run. \ No newline at end of file From f5759c12d62d3e6eeaef4aec1eb36ed32a2d07a3 Mon Sep 17 00:00:00 2001 From: vchen7629 Date: Wed, 22 Jul 2026 11:31:19 -0700 Subject: [PATCH 2/2] DCO Remediation Commit for vchen7629 I, vchen7629 , hereby add my Signed-off-by to this commit: 1efb60030200bc131245a5693754b03a8d80421e Signed-off-by: vchen7629