// STRYKE-GCP — GOOGLE CLOUD CLIENT FOR STRYKE // CLOUD STORAGE + PUB/SUB

Scope

Twelve service families ship in v0.19.x, exposed through 84 gcp__* FFI entry points and a set of typed .stk wrappers. The package is intentionally narrower than the full GCP REST surface — the goal is “useful from a shell pipeline”, not exhaustive API coverage.

Install

# from a release (no rustc on the consumer machine)
s pkg install -g github.com/MenkeTechnologies/stryke-gcp

# from a local checkout
cd ~/projects/stryke-gcp
cargo build --release            # produces target/release/libstryke_gcp.{dylib,so}
s pkg install -g .               # cdylib lands in ~/.stryke/store/gcp@<version>/

# one-liner
make install

The cdylib is dlopened in-process on first use GCP — no helper-binary fork per call. Any stryke script that declares use GCP (or a submodule like use GCP::Storage) resolves the package automatically.

Auth

Uses Application Default Credentials — the same chain as gcloud:

1. $GOOGLE_APPLICATION_CREDENTIALS pointing at a service-account JSON.
2. gcloud auth application-default login on dev machines.
3. The GCE / Cloud Run / GKE metadata server when running on GCP.

Set the project once and forget it:

export GOOGLE_CLOUD_PROJECT=my-project-id

Per call, override the project with project => "..." on any public fn. ADC discovery, metadata-server lookup, WIF, and SA-file resolution run once per stryke session — the cached credentials live in OnceCell and are reused on every subsequent call.

GCP::Storage::ls "gs://my-bucket/", project => "other-project"
GCP::PubSub::publish "my-topic", "x", project => "other-project"

Quick start: use GCP

Project / endpoint overrides apply on every public fn via project => "...". The complete reference is below; the README "API reference" section is the authoritative mirror.

API reference: use GCP

Plumbing fns plus the flat GCP::<service>_<op> entry points the namespaced wrappers delegate to.

Pure helpers — credential-free string parsing / validation (no network, no auth):

Secret Manager (flat ops under use GCP):

API reference: use GCP::Storage

ls entries: {type=>"object", key, size, content_type, md5, etag, updated, storage_class, generation} or {type=>"prefix", key} when delimiter is set.

API reference: use GCP::PubSub

Topic / subscription names accept bare (my-topic) or fully qualified (projects/PROJECT/topics/my-topic) forms. Bare names expand against $opts{project} or $GOOGLE_CLOUD_PROJECT.

API reference: use GCP::BigQuery

API reference: use GCP::Firestore

Field values cross as plain stryke data; the cdylib handles Firestore's typed encoding (stringValue / integerValue / …) in both directions. Flat forms are GCP::firestore_get / _set / _delete / _list.

API reference: use GCP::Compute

API reference: Run / Functions / Logging / Monitoring / IAM

use GCP::Run

use GCP::Functions

use GCP::Logging

use GCP::Monitoring

use GCP::IAM

Examples

Runnable .stk scripts ship under examples/. Each is read-only or eval-guarded so it exits cleanly when ADC is unreachable.

# pubsub_pump.stk core — pull → callback → ack, 5 iterations
val $n = GCP::PubSub::pump($sub,
    iterations => 5,
    max        => 10,
    callback   => sub ($m) {
        p "got $m->{message_id}: $m->{data}"
    })
p "handled $n messages"

Tests & dev workflow

cargo test                       # compiles, no live calls
s test t/                        # ADC-aware end-to-end

# opt into per-service round-trips
export STRYKE_GCP_TEST_BUCKET=my-test-bucket
export STRYKE_GCP_TEST_TOPIC=my-test-topic
export STRYKE_GCP_TEST_SUB=my-test-sub
s test t/

make            # release build
make debug
make test
make install
make clean

The suite skips cleanly when the cdylib isn't installed, when ADC isn't reachable, or when the per-service env vars are unset.

Why a package, not a builtin

GCP integration needs an auth chain (Application Default Credentials), a TLS HTTP client, and JSON serialization — fine to bundle once, opt-in. The cdylib talks to GCP's REST APIs directly via reqwest + google-cloud-auth.

The stryke side is a thin .stk wrapper that calls gcp__* FFI symbols on the cdylib; the heavy code lives in libstryke_gcp.{dylib,so}, dlopened in-process on first use GCP. Core stryke is never linked against this package's deps.

FFI layer

Each GCP::* wrapper builds a JSON args dict and calls a sibling gcp__* symbol resolved out of libstryke_gcp.{dylib,so}. The cdylib is dlopened in-process on first use GCP; a shared tokio runtime + reqwest::Client + cached ADC credentials are held in OnceCell — no fork-per-call, no re-running of ADC discovery / metadata-server / WIF / SA-file lookup on each call. Responses are JSON; errors come back as {"error": "<msg>"} and the wrapper dies with the message.

Layout

stryke-gcp/
├── Cargo.toml             # cdylib crate manifest (crate-type = ["cdylib"], publish = false)
├── src/
│   └── lib.rs            # cdylib — gcp__* extern "C" exports
├── lib/                   # stryke .stk wrapper(s) — `use GCP`, `use GCP::Storage`, …
├── stryke.toml            # stryke package manifest
├── t/                     # zunit-style tests
├── examples/              # runnable .stk examples
├── Makefile               # `make install` builds + installs
└── docs/                  # this site (GitHub Pages)

Sibling packages

Part of the stryke package family. Browse the others via the MenkeTechnologiesMeta umbrella repo:

• stryke-arrow — Apache Arrow / Parquet / Feather
• stryke-aws — S3, DynamoDB, SQS, Lambda, STS
• stryke-azure — Blob, Queues, Cosmos DB, Key Vault, Entra
• stryke-clickhouse — ClickHouse
• stryke-demo — live demos for every connector
• stryke-docker — Docker daemon API
• stryke-duckdb — embedded DuckDB SQL engine
• stryke-email — email + campaign client
• stryke-fleet — parallel expect/PTY automation
• stryke-grpc — reflection-based gRPC client
• stryke-gui — mouse / keyboard / screen / clipboard automation
• stryke-k8s — Kubernetes
• stryke-kafka — Apache Kafka
• stryke-mcpd — MCP servers without a runtime
• stryke-mongo — MongoDB
• stryke-mssql — Microsoft SQL Server
• stryke-mysql — MySQL / MariaDB
• stryke-neo4j — Neo4j graph (Bolt)
• stryke-office — Office docs / PDF / images
• stryke-parquet — Parquet file inspector
• stryke-polars — Polars + ndarray + linalg + FFT
• stryke-postgres — PostgreSQL
• stryke-redis — Redis / Valkey
• stryke-scrape — web scraping / crawling
• stryke-scylla — ScyllaDB / Cassandra
• stryke-search — Elasticsearch / OpenSearch
• stryke-selenium — browser automation (WebDriver)
• stryke-spark — Spark Connect (no JVM)
• stryke-utils — pure-stryke utility belt
• stryke-zmq — ZeroMQ messaging