boost-factory-gcp-api
Use when configuring shared GCP API options (credentials, endpoint, user-agent) consumed by all cloud.google.com/* factories — bigquery, firestore, pubsub. Provided by github.com/xgodev/boost/factory/contrib/cloud.google.com/api/v0. Covers ConfigAdd and how this layer composes inside the GCP service factories. Triggers on imports under factory/contrib/cloud.google.com/api/, on questions about GCP credentials override, custom endpoints (emulator), or user-agent string in a boost service.
Works with
--- name: boost-factory-gcp-api description: Use when configuring shared GCP API options (credentials, endpoint, user-agent) consumed by all cloud.google.com/* factories — bigquery, firestore, pubsub. Provided by github.com/xgodev/boost/factory/contrib/cloud.google.com/api/v0. Covers ConfigAdd and how this layer composes inside the GCP service factories. Triggers on imports under factory/contrib/cloud.google.com/api/, on questions about GCP credentials override, custom endpoints (emulator), or user-agent string in a boost service. license: MIT --- **REQUIRED BACKGROUND:** `boost-start`, `boost-wrapper-config`. Composed by `boost-factory-bigquery`, `boost-factory-firestore`, `boost-factory-pubsub`. ## What it provides Shared GCP API options (credentials JSON, endpoint URL, user-agent) registered under `boost.factory.gcp.api.*` and composed by every concrete GCP factory at `<root>.apiOptions.*`. You rarely import this skill's package directly — you configure its keys instead. ## Tunables - `apiOptions.projectID` — GCP project - `apiOptions.credentialsJSON` / `apiOptions.credentialsFile` — service-account override - `apiOptions.endpoint` — emulator URL (e.g., `localhost:8085` for the Pub/Sub emulator) or private endpoint - `apiOptions.userAgent` — header used in API calls Override per-service: a dedicated emulator for the BigQuery factory only: ``` BOOST_FACTORY_GCP_BIGQUERY_APIOPTIONS_ENDPOINT=localhost:9050 ``` ## Red flags | Red flag | Fix | |---|---| | Setting GCP credentials at the cloud-google service factory level when multiple services share them | Set under `boost.factory.gcp.api.*` once; service factories inherit | | Pointing one env var at all GCP services when only one needs an emulator | Use the per-service `apiOptions.endpoint` override | | Hardcoded service-account JSON in the repo | Provide via Vault (`boost-factory-vault`) or workload identity |
More DevOps & Infrastructure skills
azure-ai
microsoft/azure-skills
Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.
appinsights-instrumentation
microsoft/azure-skills
Guidance for instrumenting webapps with Azure Application Insights. Provides telemetry patterns, SDK setup, and configuration references. WHEN: how to instrument app, App Insights SDK, telemetry patterns, what is App Insights, Application Insights guidance, instrumentation examples, APM best practices.
azure-storage
microsoft/azure-skills
Azure Storage Services including Blob Storage, File Shares, Queue Storage, Table Storage, and Data Lake. Answers questions about storage access tiers (hot, cool, cold, archive), when to use each tier, and tier comparison. Provides object storage, SMB file shares, async messaging, NoSQL key-value, and big data analytics. Includes lifecycle management. USE FOR: blob storage, file shares, queue storage, table storage, data lake, upload files, download blobs, storage accounts, access tiers, storage tiers, hot cool cold archive, storage tier comparison, when to use storage tiers, lifecycle management, Azure Storage concepts. DO NOT USE FOR: SQL databases, Cosmos DB (use azure-prepare), messaging with Event Hubs or Service Bus (use azure-messaging).
