@raishin/vanguard-frontier-agentic 3.19.0 → 3.20.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.claude-plugin/marketplace.json +2 -2
- package/.claude-plugin/plugin.json +8 -1
- package/.cursor-plugin/plugin.json +8 -1
- package/.github/plugin/marketplace.json +1 -1
- package/README.md +21 -21
- package/agents/AGENTS.md +4 -4
- package/agents/README.md +7 -7
- package/agents/alibaba/alibaba-tablestore-architect-agent/AGENT.md +54 -0
- package/agents/alibaba/alibaba-tablestore-architect-agent/harnesses/claude-code.agent.md +37 -0
- package/agents/alibaba/alibaba-tablestore-architect-agent/harnesses/codex.toml +11 -0
- package/agents/alibaba/alibaba-tablestore-architect-agent/harnesses/copilot.agent.md +43 -0
- package/agents/alibaba/alibaba-tablestore-architect-agent/harnesses/cursor.agent.md +38 -0
- package/agents/alibaba/alibaba-tablestore-architect-agent/harnesses/gemini.agent.md +39 -0
- package/agents/alibaba/alibaba-tablestore-architect-agent/harnesses/kiro-cli.agent.json +5 -0
- package/agents/alibaba/alibaba-tablestore-architect-agent/harnesses/kiro-ide.agent.md +37 -0
- package/agents/alibaba/alibaba-tablestore-architect-agent/metadata.json +39 -0
- package/agents/aws/aws-dynamodb-patterns-agent/AGENT.md +53 -0
- package/agents/aws/aws-dynamodb-patterns-agent/harnesses/claude-code.agent.md +36 -0
- package/agents/aws/aws-dynamodb-patterns-agent/harnesses/codex.toml +23 -0
- package/agents/aws/aws-dynamodb-patterns-agent/harnesses/copilot.agent.md +42 -0
- package/agents/aws/aws-dynamodb-patterns-agent/harnesses/cursor.agent.md +38 -0
- package/agents/aws/aws-dynamodb-patterns-agent/harnesses/gemini.agent.md +38 -0
- package/agents/aws/aws-dynamodb-patterns-agent/harnesses/kiro-cli.agent.json +5 -0
- package/agents/aws/aws-dynamodb-patterns-agent/harnesses/kiro-ide.agent.md +36 -0
- package/agents/aws/aws-dynamodb-patterns-agent/metadata.json +39 -0
- package/agents/azure/azure-cosmosdb-application-developer-agent/metadata.json +4 -0
- package/agents/azure/azure-cosmosdb-pattern-agent/AGENT.md +53 -0
- package/agents/azure/azure-cosmosdb-pattern-agent/harnesses/claude-code.agent.md +36 -0
- package/agents/azure/azure-cosmosdb-pattern-agent/harnesses/codex.toml +23 -0
- package/agents/azure/azure-cosmosdb-pattern-agent/harnesses/copilot.agent.md +42 -0
- package/agents/azure/azure-cosmosdb-pattern-agent/harnesses/cursor.agent.md +37 -0
- package/agents/azure/azure-cosmosdb-pattern-agent/harnesses/gemini.agent.md +38 -0
- package/agents/azure/azure-cosmosdb-pattern-agent/harnesses/kiro-cli.agent.json +5 -0
- package/agents/azure/azure-cosmosdb-pattern-agent/harnesses/kiro-ide.agent.md +36 -0
- package/agents/azure/azure-cosmosdb-pattern-agent/metadata.json +38 -0
- package/agents/gcp/gcp-bigtable-architect-agent/AGENT.md +54 -0
- package/agents/gcp/gcp-bigtable-architect-agent/harnesses/claude-code.agent.md +37 -0
- package/agents/gcp/gcp-bigtable-architect-agent/harnesses/codex.toml +11 -0
- package/agents/gcp/gcp-bigtable-architect-agent/harnesses/copilot.agent.md +43 -0
- package/agents/gcp/gcp-bigtable-architect-agent/harnesses/cursor.agent.md +38 -0
- package/agents/gcp/gcp-bigtable-architect-agent/harnesses/gemini.agent.md +39 -0
- package/agents/gcp/gcp-bigtable-architect-agent/harnesses/kiro-cli.agent.json +5 -0
- package/agents/gcp/gcp-bigtable-architect-agent/harnesses/kiro-ide.agent.md +37 -0
- package/agents/gcp/gcp-bigtable-architect-agent/metadata.json +39 -0
- package/agents/huawei/huawei-geminidb-architect-agent/AGENT.md +54 -0
- package/agents/huawei/huawei-geminidb-architect-agent/harnesses/claude-code.agent.md +37 -0
- package/agents/huawei/huawei-geminidb-architect-agent/harnesses/codex.toml +11 -0
- package/agents/huawei/huawei-geminidb-architect-agent/harnesses/copilot.agent.md +43 -0
- package/agents/huawei/huawei-geminidb-architect-agent/harnesses/cursor.agent.md +38 -0
- package/agents/huawei/huawei-geminidb-architect-agent/harnesses/gemini.agent.md +39 -0
- package/agents/huawei/huawei-geminidb-architect-agent/harnesses/kiro-cli.agent.json +5 -0
- package/agents/huawei/huawei-geminidb-architect-agent/harnesses/kiro-ide.agent.md +37 -0
- package/agents/huawei/huawei-geminidb-architect-agent/metadata.json +38 -0
- package/agents/oci/oci-nosql-database-architect-agent/AGENT.md +54 -0
- package/agents/oci/oci-nosql-database-architect-agent/harnesses/claude-code.agent.md +37 -0
- package/agents/oci/oci-nosql-database-architect-agent/harnesses/codex.toml +11 -0
- package/agents/oci/oci-nosql-database-architect-agent/harnesses/copilot.agent.md +43 -0
- package/agents/oci/oci-nosql-database-architect-agent/harnesses/cursor.agent.md +39 -0
- package/agents/oci/oci-nosql-database-architect-agent/harnesses/gemini.agent.md +39 -0
- package/agents/oci/oci-nosql-database-architect-agent/harnesses/kiro-cli.agent.json +5 -0
- package/agents/oci/oci-nosql-database-architect-agent/harnesses/kiro-ide.agent.md +37 -0
- package/agents/oci/oci-nosql-database-architect-agent/metadata.json +39 -0
- package/agents/oci/oci-nosql-pattern-agent/AGENT.md +53 -0
- package/agents/oci/oci-nosql-pattern-agent/harnesses/claude-code.agent.md +36 -0
- package/agents/oci/oci-nosql-pattern-agent/harnesses/codex.toml +23 -0
- package/agents/oci/oci-nosql-pattern-agent/harnesses/copilot.agent.md +42 -0
- package/agents/oci/oci-nosql-pattern-agent/harnesses/cursor.agent.md +38 -0
- package/agents/oci/oci-nosql-pattern-agent/harnesses/gemini.agent.md +38 -0
- package/agents/oci/oci-nosql-pattern-agent/harnesses/kiro-cli.agent.json +5 -0
- package/agents/oci/oci-nosql-pattern-agent/harnesses/kiro-ide.agent.md +36 -0
- package/agents/oci/oci-nosql-pattern-agent/metadata.json +38 -0
- package/catalog/agents.json +204 -1
- package/catalog/asset-integrity.json +601 -61
- package/catalog/install-roles.json +19 -1
- package/catalog/model-assignments.json +231 -0
- package/catalog/skill-manifest.json +1603 -56
- package/catalog/skills.json +314 -14
- package/package.json +7 -2
- package/plugins/vanguard-frontier-agentic/.codex-plugin/plugin.json +1 -1
- package/powers/vanguard-alibaba/POWER.md +1 -1
- package/powers/vanguard-aws/POWER.md +1 -1
- package/powers/vanguard-azure/POWER.md +1 -1
- package/powers/vanguard-gcp/POWER.md +1 -1
- package/powers/vanguard-huawei/POWER.md +1 -1
- package/powers/vanguard-oci/POWER.md +1 -1
- package/skills/alibaba/README.md +2 -1
- package/skills/alibaba/alibaba-maestro/SKILL.md +2 -1
- package/skills/alibaba/alibaba-tablestore-architect/SKILL.md +69 -0
- package/skills/alibaba/alibaba-tablestore-architect/metadata.json +28 -0
- package/skills/alibaba/alibaba-tablestore-architect/references/commands/audit/live.md +110 -0
- package/skills/alibaba/alibaba-tablestore-architect/references/commands/audit/offline.md +119 -0
- package/skills/alibaba/alibaba-tablestore-architect/references/commands/audit.md +22 -0
- package/skills/alibaba/alibaba-tablestore-architect/references/evidence-ledger.md +87 -0
- package/skills/alibaba/alibaba-tablestore-architect/references/operations.md +190 -0
- package/skills/alibaba/alibaba-tablestore-architect/references/tablestore-design-guide.md +159 -0
- package/skills/aws/aws-documentdb-architect/SKILL.md +43 -0
- package/skills/aws/aws-documentdb-architect/metadata.json +26 -0
- package/skills/aws/aws-documentdb-architect/references/commands/audit/live.md +135 -0
- package/skills/aws/aws-documentdb-architect/references/commands/audit/offline.md +127 -0
- package/skills/aws/aws-documentdb-architect/references/commands/audit.md +23 -0
- package/skills/aws/aws-documentdb-architect/references/evidence-ledger.md +52 -0
- package/skills/aws/aws-documentdb-architect/references/official-sources.md +15 -0
- package/skills/aws/aws-documentdb-architect/references/operations.md +165 -0
- package/skills/aws/aws-documentdb-architect/references/safety-checklist.md +22 -0
- package/skills/aws/aws-documentdb-architect/references/workflow-and-output.md +22 -0
- package/skills/aws/aws-dynamodb-data-modeling-performance-review/SKILL.md +5 -3
- package/skills/aws/aws-dynamodb-data-modeling-performance-review/metadata.json +7 -3
- package/skills/aws/aws-dynamodb-data-modeling-performance-review/references/consistency-indexing-replication.md +103 -0
- package/skills/aws/aws-dynamodb-data-modeling-performance-review/references/evidence-ledger.md +38 -0
- package/skills/aws/aws-dynamodb-patterns/CHANGELOG.md +87 -0
- package/skills/aws/aws-dynamodb-patterns/README.md +132 -0
- package/skills/aws/aws-dynamodb-patterns/SKILL.md +82 -0
- package/skills/aws/aws-dynamodb-patterns/assets/bedrock-embedding-input.json +6 -0
- package/skills/aws/aws-dynamodb-patterns/assets/content-review.json +6 -0
- package/skills/aws/aws-dynamodb-patterns/assets/create-table-with-lsi.json +41 -0
- package/skills/aws/aws-dynamodb-patterns/assets/create-table.json +27 -0
- package/skills/aws/aws-dynamodb-patterns/assets/create-table.sh +37 -0
- package/skills/aws/aws-dynamodb-patterns/assets/embedding-flow.py +89 -0
- package/skills/aws/aws-dynamodb-patterns/assets/query-input.json +13 -0
- package/skills/aws/aws-dynamodb-patterns/assets/query-pages.mjs +54 -0
- package/skills/aws/aws-dynamodb-patterns/assets/stream-read-policy.json +11 -0
- package/skills/aws/aws-dynamodb-patterns/assets/table-index-read-policy.json +20 -0
- package/skills/aws/aws-dynamodb-patterns/assets/table-resource-policy.json +22 -0
- package/skills/aws/aws-dynamodb-patterns/assets/table.cfn.yaml +55 -0
- package/skills/aws/aws-dynamodb-patterns/assets/typed-vector-item.json +15 -0
- package/skills/aws/aws-dynamodb-patterns/assets/vector-create-table.json +23 -0
- package/skills/aws/aws-dynamodb-patterns/assets/vector-search-policy.json +11 -0
- package/skills/aws/aws-dynamodb-patterns/assets/vector-search.json +10 -0
- package/skills/aws/aws-dynamodb-patterns/assets/vector-table.cfn.yaml +41 -0
- package/skills/aws/aws-dynamodb-patterns/evals/audit.test.py +87 -0
- package/skills/aws/aws-dynamodb-patterns/evals/backup-restore.test.py +163 -0
- package/skills/aws/aws-dynamodb-patterns/evals/commands.test.py +185 -0
- package/skills/aws/aws-dynamodb-patterns/evals/create-table.test.py +99 -0
- package/skills/aws/aws-dynamodb-patterns/evals/data-vectors-maintenance.test.py +201 -0
- package/skills/aws/aws-dynamodb-patterns/evals/embedding-commands.test.py +162 -0
- package/skills/aws/aws-dynamodb-patterns/evals/embedding-flow.test.py +167 -0
- package/skills/aws/aws-dynamodb-patterns/evals/eval.md +328 -0
- package/skills/aws/aws-dynamodb-patterns/evals/evals.json +185 -0
- package/skills/aws/aws-dynamodb-patterns/evals/modes.test.py +195 -0
- package/skills/aws/aws-dynamodb-patterns/evals/operations.test.py +288 -0
- package/skills/aws/aws-dynamodb-patterns/evals/query-pages.test.mjs +156 -0
- package/skills/aws/aws-dynamodb-patterns/evals/readme-and-loading.test.py +69 -0
- package/skills/aws/aws-dynamodb-patterns/evals/verify.py +166 -0
- package/skills/aws/aws-dynamodb-patterns/metadata.json +28 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/README.md +32 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/audit/live.md +64 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/audit/offline.md +28 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/audit.md +65 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/aws-cli.md +206 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/backup/on-demand.md +36 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/backup/pitr.md +41 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/backup.md +27 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/design.md +47 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/embedding.md +200 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/feature-plan.md +56 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/help.md +28 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/performance-test.md +95 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/recovery-target.md +47 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/refactor.md +82 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/restore/on-demand.md +32 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/restore/pitr.md +42 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/restore.md +76 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/select.md +22 -0
- package/skills/aws/aws-dynamodb-patterns/references/data-types-and-vectors.md +175 -0
- package/skills/aws/aws-dynamodb-patterns/references/embedding-integrations.md +237 -0
- package/skills/aws/aws-dynamodb-patterns/references/encryption.md +156 -0
- package/skills/aws/aws-dynamodb-patterns/references/evidence-index.md +116 -0
- package/skills/aws/aws-dynamodb-patterns/references/evidence-ledger.md +373 -0
- package/skills/aws/aws-dynamodb-patterns/references/iam-and-access.md +173 -0
- package/skills/aws/aws-dynamodb-patterns/references/language-adapters.md +251 -0
- package/skills/aws/aws-dynamodb-patterns/references/lsi-vs-gsi.md +116 -0
- package/skills/aws/aws-dynamodb-patterns/references/maintenance.md +56 -0
- package/skills/aws/aws-dynamodb-patterns/references/modeling.md +131 -0
- package/skills/aws/aws-dynamodb-patterns/references/monitoring.md +137 -0
- package/skills/aws/aws-dynamodb-patterns/references/official-sources.md +34 -0
- package/skills/aws/aws-dynamodb-patterns/references/operations.md +130 -0
- package/skills/aws/aws-dynamodb-patterns/references/provisioning.md +110 -0
- package/skills/aws/aws-dynamodb-patterns/references/recovery-and-replicas.md +148 -0
- package/skills/aws/aws-dynamodb-patterns/references/runtime-contract.md +140 -0
- package/skills/aws/aws-dynamodb-patterns/references/safety-checklist.md +35 -0
- package/skills/aws/aws-dynamodb-patterns/references/sources.md +170 -0
- package/skills/aws/aws-dynamodb-patterns/references/streams-and-dax.md +160 -0
- package/skills/aws/aws-dynamodb-patterns/references/workflow-and-output.md +34 -0
- package/skills/aws/aws-dynamodb-patterns/references/workflow.md +133 -0
- package/skills/aws/aws-dynamodb-patterns/scripts/review_due.py +61 -0
- package/skills/aws/aws-dynamodb-patterns/scripts/select_mode.py +127 -0
- package/skills/aws/aws-keyspaces-architect/SKILL.md +43 -0
- package/skills/aws/aws-keyspaces-architect/metadata.json +26 -0
- package/skills/aws/aws-keyspaces-architect/references/commands/audit/live.md +118 -0
- package/skills/aws/aws-keyspaces-architect/references/commands/audit/offline.md +125 -0
- package/skills/aws/aws-keyspaces-architect/references/commands/audit.md +22 -0
- package/skills/aws/aws-keyspaces-architect/references/evidence-ledger.md +49 -0
- package/skills/aws/aws-keyspaces-architect/references/official-sources.md +15 -0
- package/skills/aws/aws-keyspaces-architect/references/operations.md +154 -0
- package/skills/aws/aws-keyspaces-architect/references/safety-checklist.md +22 -0
- package/skills/aws/aws-keyspaces-architect/references/workflow-and-output.md +22 -0
- package/skills/aws/aws-maestro/SKILL.md +1 -1
- package/skills/aws/aws-maestro/metadata.json +1 -1
- package/skills/aws/aws-maestro/references/workflow-and-output.md +1 -0
- package/skills/azure/azure-cosmosdb-application-developer/SKILL.md +4 -2
- package/skills/azure/azure-cosmosdb-application-developer/metadata.json +1 -1
- package/skills/azure/azure-cosmosdb-pattern/CHANGELOG.md +10 -0
- package/skills/azure/azure-cosmosdb-pattern/README.md +102 -0
- package/skills/azure/azure-cosmosdb-pattern/SKILL.md +69 -0
- package/skills/azure/azure-cosmosdb-pattern/assets/account.arm.json +59 -0
- package/skills/azure/azure-cosmosdb-pattern/assets/content-review.json +9 -0
- package/skills/azure/azure-cosmosdb-pattern/assets/indexing-policy.json +7 -0
- package/skills/azure/azure-cosmosdb-pattern/assets/order.json +10 -0
- package/skills/azure/azure-cosmosdb-pattern/assets/provision.sh +32 -0
- package/skills/azure/azure-cosmosdb-pattern/assets/runtime.mjs +99 -0
- package/skills/azure/azure-cosmosdb-pattern/assets/vector-indexing-policy.json +7 -0
- package/skills/azure/azure-cosmosdb-pattern/assets/vector-policy.json +3 -0
- package/skills/azure/azure-cosmosdb-pattern/evals/eval.md +32 -0
- package/skills/azure/azure-cosmosdb-pattern/evals/fixtures/recovery-continuous.json +28 -0
- package/skills/azure/azure-cosmosdb-pattern/evals/prompts.json +24 -0
- package/skills/azure/azure-cosmosdb-pattern/evals/report.md +54 -0
- package/skills/azure/azure-cosmosdb-pattern/evals/runtime.test.mjs +146 -0
- package/skills/azure/azure-cosmosdb-pattern/evals/source-evidence.json +28 -0
- package/skills/azure/azure-cosmosdb-pattern/evals/test_package.py +355 -0
- package/skills/azure/azure-cosmosdb-pattern/metadata.json +25 -0
- package/skills/azure/azure-cosmosdb-pattern/references/access-control.md +42 -0
- package/skills/azure/azure-cosmosdb-pattern/references/change-feed-and-integrations.md +31 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/audit/live.md +17 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/audit/offline.md +15 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/audit.md +8 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/azure-cli.md +39 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/backup/continuous.md +30 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/backup/periodic.md +28 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/backup.md +11 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/design.md +13 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/feature-plan.md +18 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/help.md +13 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/performance-test.md +24 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/recovery-target.md +30 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/refactor.md +14 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/restore/continuous-deleted-resource.md +55 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/restore/continuous-new-account.md +50 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/restore/periodic-support.md +27 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/restore.md +13 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/select.md +11 -0
- package/skills/azure/azure-cosmosdb-pattern/references/data-types-and-vectors.md +51 -0
- package/skills/azure/azure-cosmosdb-pattern/references/embedding-integrations.md +56 -0
- package/skills/azure/azure-cosmosdb-pattern/references/encryption.md +53 -0
- package/skills/azure/azure-cosmosdb-pattern/references/evidence-index.md +72 -0
- package/skills/azure/azure-cosmosdb-pattern/references/evidence-ledger.md +174 -0
- package/skills/azure/azure-cosmosdb-pattern/references/indexing-and-capacity.md +37 -0
- package/skills/azure/azure-cosmosdb-pattern/references/language-adapters.md +112 -0
- package/skills/azure/azure-cosmosdb-pattern/references/maintenance.md +19 -0
- package/skills/azure/azure-cosmosdb-pattern/references/modeling.md +44 -0
- package/skills/azure/azure-cosmosdb-pattern/references/monitoring.md +23 -0
- package/skills/azure/azure-cosmosdb-pattern/references/provisioning.md +61 -0
- package/skills/azure/azure-cosmosdb-pattern/references/recovery.md +31 -0
- package/skills/azure/azure-cosmosdb-pattern/references/replication.md +22 -0
- package/skills/azure/azure-cosmosdb-pattern/references/runtime-contract.md +43 -0
- package/skills/azure/azure-cosmosdb-pattern/references/sources.md +61 -0
- package/skills/azure/azure-cosmosdb-pattern/references/workflow.md +18 -0
- package/skills/azure/azure-cosmosdb-pattern/scripts/recovery_guard.py +96 -0
- package/skills/azure/azure-cosmosdb-pattern/scripts/review_due.py +26 -0
- package/skills/azure/azure-cosmosdb-pattern/scripts/select_mode.py +108 -0
- package/skills/azure/azure-cosmosdb-pattern/scripts/validate_assets.py +53 -0
- package/skills/azure/azure-cosmosdb-platform-operator/SKILL.md +6 -2
- package/skills/azure/azure-cosmosdb-platform-operator/metadata.json +6 -3
- package/skills/azure/azure-cosmosdb-platform-operator/references/commands/audit/live.md +180 -0
- package/skills/azure/azure-cosmosdb-platform-operator/references/commands/audit/offline.md +160 -0
- package/skills/azure/azure-cosmosdb-platform-operator/references/commands/audit.md +26 -0
- package/skills/azure/azure-cosmosdb-platform-operator/references/consistency-capacity-security.md +136 -0
- package/skills/azure/azure-cosmosdb-platform-operator/references/cosmosdb-platform-operations.md +1 -1
- package/skills/azure/azure-cosmosdb-platform-operator/references/evidence-ledger.md +242 -0
- package/skills/azure/azure-cosmosdb-platform-operator/references/operations-cassandra.md +178 -0
- package/skills/azure/azure-cosmosdb-platform-operator/references/operations-mongodb.md +202 -0
- package/skills/azure/azure-cosmosdb-platform-operator/references/operations.md +126 -0
- package/skills/azure/azure-maestro/SKILL.md +1 -0
- package/skills/gcp/README.md +2 -1
- package/skills/gcp/gcp-bigtable-architect/SKILL.md +71 -0
- package/skills/gcp/gcp-bigtable-architect/metadata.json +28 -0
- package/skills/gcp/gcp-bigtable-architect/references/bigtable-design-guide.md +156 -0
- package/skills/gcp/gcp-bigtable-architect/references/commands/audit/live.md +122 -0
- package/skills/gcp/gcp-bigtable-architect/references/commands/audit/offline.md +140 -0
- package/skills/gcp/gcp-bigtable-architect/references/commands/audit.md +21 -0
- package/skills/gcp/gcp-bigtable-architect/references/evidence-ledger.md +83 -0
- package/skills/gcp/gcp-bigtable-architect/references/operations.md +111 -0
- package/skills/gcp/gcp-firebase-developer/SKILL.md +6 -3
- package/skills/gcp/gcp-firebase-developer/metadata.json +14 -4
- package/skills/gcp/gcp-firebase-developer/references/commands/audit/live.md +124 -0
- package/skills/gcp/gcp-firebase-developer/references/commands/audit/offline.md +146 -0
- package/skills/gcp/gcp-firebase-developer/references/commands/audit.md +27 -0
- package/skills/gcp/gcp-firebase-developer/references/evidence-ledger.md +190 -0
- package/skills/gcp/gcp-firebase-developer/references/firestore-mongodb-operations.md +189 -0
- package/skills/gcp/gcp-firebase-developer/references/firestore-operations.md +202 -0
- package/skills/gcp/gcp-firebase-developer/references/firestore.md +122 -0
- package/skills/gcp/gcp-maestro/SKILL.md +2 -1
- package/skills/huawei/README.md +2 -1
- package/skills/huawei/huawei-gaussdb-rds-dba/SKILL.md +7 -4
- package/skills/huawei/huawei-gaussdb-rds-dba/metadata.json +12 -4
- package/skills/huawei/huawei-gaussdb-rds-dba/references/commands/audit/live.md +68 -0
- package/skills/huawei/huawei-gaussdb-rds-dba/references/commands/audit/offline.md +106 -0
- package/skills/huawei/huawei-gaussdb-rds-dba/references/commands/audit.md +23 -0
- package/skills/huawei/huawei-gaussdb-rds-dba/references/dds-operations.md +135 -0
- package/skills/huawei/huawei-gaussdb-rds-dba/references/evidence-ledger.md +87 -0
- package/skills/huawei/huawei-geminidb-architect/SKILL.md +68 -0
- package/skills/huawei/huawei-geminidb-architect/metadata.json +26 -0
- package/skills/huawei/huawei-geminidb-architect/references/commands/audit/live.md +68 -0
- package/skills/huawei/huawei-geminidb-architect/references/commands/audit/offline.md +108 -0
- package/skills/huawei/huawei-geminidb-architect/references/commands/audit.md +23 -0
- package/skills/huawei/huawei-geminidb-architect/references/evidence-ledger.md +83 -0
- package/skills/huawei/huawei-geminidb-architect/references/geminidb-design-guide.md +114 -0
- package/skills/huawei/huawei-geminidb-architect/references/operations.md +135 -0
- package/skills/huawei/huawei-maestro/SKILL.md +2 -1
- package/skills/ionos/ionos-live-database-lifecycle-guard/SKILL.md +2 -0
- package/skills/ionos/ionos-live-database-lifecycle-guard/references/commands/audit/live.md +87 -0
- package/skills/ionos/ionos-live-database-lifecycle-guard/references/commands/audit/offline.md +109 -0
- package/skills/ionos/ionos-live-database-lifecycle-guard/references/commands/audit.md +27 -0
- package/skills/ionos/ionos-live-database-lifecycle-guard/references/evidence-ledger.md +69 -0
- package/skills/ionos/ionos-live-database-lifecycle-guard/references/mongodb-operations.md +220 -0
- package/skills/oci/README.md +6 -1
- package/skills/oci/oci-nosql-database-architect/SKILL.md +73 -0
- package/skills/oci/oci-nosql-database-architect/metadata.json +28 -0
- package/skills/oci/oci-nosql-database-architect/references/commands/audit/live.md +136 -0
- package/skills/oci/oci-nosql-database-architect/references/commands/audit/offline.md +150 -0
- package/skills/oci/oci-nosql-database-architect/references/commands/audit.md +28 -0
- package/skills/oci/oci-nosql-database-architect/references/evidence-ledger.md +96 -0
- package/skills/oci/oci-nosql-database-architect/references/nosql-design-guide.md +194 -0
- package/skills/oci/oci-nosql-database-architect/references/operations.md +194 -0
- package/skills/oci/oci-nosql-database-architect/references/sdk-matrix.md +43 -0
- package/skills/oci/oci-nosql-pattern/CHANGELOG.md +8 -0
- package/skills/oci/oci-nosql-pattern/README.md +81 -0
- package/skills/oci/oci-nosql-pattern/SKILL.md +62 -0
- package/skills/oci/oci-nosql-pattern/assets/content-review.json +10 -0
- package/skills/oci/oci-nosql-pattern/assets/create-table.sh +32 -0
- package/skills/oci/oci-nosql-pattern/assets/index-keys.json +11 -0
- package/skills/oci/oci-nosql-pattern/assets/migrator-export.json +22 -0
- package/skills/oci/oci-nosql-pattern/assets/migrator-import.json +29 -0
- package/skills/oci/oci-nosql-pattern/assets/orders.ddl +9 -0
- package/skills/oci/oci-nosql-pattern/assets/orders.tf +46 -0
- package/skills/oci/oci-nosql-pattern/assets/query-pages.mjs +33 -0
- package/skills/oci/oci-nosql-pattern/assets/query.json +13 -0
- package/skills/oci/oci-nosql-pattern/assets/query.sql +1 -0
- package/skills/oci/oci-nosql-pattern/assets/recovery-manifest.example.json +35 -0
- package/skills/oci/oci-nosql-pattern/assets/row.json +10 -0
- package/skills/oci/oci-nosql-pattern/assets/table-limits.json +6 -0
- package/skills/oci/oci-nosql-pattern/evals/cli-shapes.json +222 -0
- package/skills/oci/oci-nosql-pattern/evals/eval.md +26 -0
- package/skills/oci/oci-nosql-pattern/evals/prompts.json +89 -0
- package/skills/oci/oci-nosql-pattern/evals/report.md +41 -0
- package/skills/oci/oci-nosql-pattern/evals/test_package.py +350 -0
- package/skills/oci/oci-nosql-pattern/evals/test_runtime.mjs +77 -0
- package/skills/oci/oci-nosql-pattern/metadata.json +25 -0
- package/skills/oci/oci-nosql-pattern/references/access.md +29 -0
- package/skills/oci/oci-nosql-pattern/references/commands/audit/live.md +10 -0
- package/skills/oci/oci-nosql-pattern/references/commands/audit/offline.md +8 -0
- package/skills/oci/oci-nosql-pattern/references/commands/audit.md +6 -0
- package/skills/oci/oci-nosql-pattern/references/commands/backup/migrator.md +12 -0
- package/skills/oci/oci-nosql-pattern/references/commands/backup/sdk.md +10 -0
- package/skills/oci/oci-nosql-pattern/references/commands/backup.md +7 -0
- package/skills/oci/oci-nosql-pattern/references/commands/design.md +10 -0
- package/skills/oci/oci-nosql-pattern/references/commands/feature-plan.md +10 -0
- package/skills/oci/oci-nosql-pattern/references/commands/help.md +8 -0
- package/skills/oci/oci-nosql-pattern/references/commands/performance-test.md +12 -0
- package/skills/oci/oci-nosql-pattern/references/commands/refactor.md +9 -0
- package/skills/oci/oci-nosql-pattern/references/commands/restore/migrator.md +13 -0
- package/skills/oci/oci-nosql-pattern/references/commands/restore/sdk.md +11 -0
- package/skills/oci/oci-nosql-pattern/references/commands/restore.md +8 -0
- package/skills/oci/oci-nosql-pattern/references/commands/select.md +8 -0
- package/skills/oci/oci-nosql-pattern/references/embedding-integrations.md +25 -0
- package/skills/oci/oci-nosql-pattern/references/encryption.md +18 -0
- package/skills/oci/oci-nosql-pattern/references/evidence-index.md +44 -0
- package/skills/oci/oci-nosql-pattern/references/evidence-ledger.md +73 -0
- package/skills/oci/oci-nosql-pattern/references/indexes.md +19 -0
- package/skills/oci/oci-nosql-pattern/references/language-adapters.md +160 -0
- package/skills/oci/oci-nosql-pattern/references/maintenance.md +15 -0
- package/skills/oci/oci-nosql-pattern/references/modeling.md +26 -0
- package/skills/oci/oci-nosql-pattern/references/monitoring.md +21 -0
- package/skills/oci/oci-nosql-pattern/references/provisioning.md +44 -0
- package/skills/oci/oci-nosql-pattern/references/recovery-boundary.md +32 -0
- package/skills/oci/oci-nosql-pattern/references/replicas.md +18 -0
- package/skills/oci/oci-nosql-pattern/references/runtime-contract.md +23 -0
- package/skills/oci/oci-nosql-pattern/references/sources.md +57 -0
- package/skills/oci/oci-nosql-pattern/references/ttl.md +19 -0
- package/skills/oci/oci-nosql-pattern/references/types-and-vectors.md +27 -0
- package/skills/oci/oci-nosql-pattern/scripts/check_recovery.py +52 -0
- package/skills/oci/oci-nosql-pattern/scripts/review_due.py +32 -0
- package/skills/oci/oci-nosql-pattern/scripts/select_mode.py +96 -0
- package/skills/ovhcloud/ovhcloud-mongodb-architect/SKILL.md +43 -0
- package/skills/ovhcloud/ovhcloud-mongodb-architect/metadata.json +25 -0
- package/skills/ovhcloud/ovhcloud-mongodb-architect/references/commands/audit/live.md +90 -0
- package/skills/ovhcloud/ovhcloud-mongodb-architect/references/commands/audit/offline.md +112 -0
- package/skills/ovhcloud/ovhcloud-mongodb-architect/references/commands/audit.md +24 -0
- package/skills/ovhcloud/ovhcloud-mongodb-architect/references/evidence-ledger.md +93 -0
- package/skills/ovhcloud/ovhcloud-mongodb-architect/references/official-sources.md +15 -0
- package/skills/ovhcloud/ovhcloud-mongodb-architect/references/operations.md +216 -0
- package/skills/ovhcloud/ovhcloud-mongodb-architect/references/safety-checklist.md +22 -0
- package/skills/ovhcloud/ovhcloud-mongodb-architect/references/workflow-and-output.md +22 -0
- package/skills/scaleway/scaleway-managed-mongodb-architect/SKILL.md +43 -0
- package/skills/scaleway/scaleway-managed-mongodb-architect/metadata.json +24 -0
- package/skills/scaleway/scaleway-managed-mongodb-architect/references/commands/audit/live.md +99 -0
- package/skills/scaleway/scaleway-managed-mongodb-architect/references/commands/audit/offline.md +114 -0
- package/skills/scaleway/scaleway-managed-mongodb-architect/references/commands/audit.md +24 -0
- package/skills/scaleway/scaleway-managed-mongodb-architect/references/evidence-ledger.md +43 -0
- package/skills/scaleway/scaleway-managed-mongodb-architect/references/official-sources.md +14 -0
- package/skills/scaleway/scaleway-managed-mongodb-architect/references/operations.md +114 -0
- package/skills/scaleway/scaleway-managed-mongodb-architect/references/safety-checklist.md +22 -0
- package/skills/scaleway/scaleway-managed-mongodb-architect/references/workflow-and-output.md +22 -0
- package/templates/nosql-audit-template.md +127 -0
- package/templates/nosql-operations-template.md +60 -0
- package/tests/_generate_maestro_routing_fixtures.py +11 -0
- package/tests/fixtures/README.md +2 -2
- package/tests/fixtures/alibaba-maestro-routing/expected/050-happy-tablestore-partition-key.json +6 -0
- package/tests/fixtures/alibaba-maestro-routing/expected/adv-tablestore-not-polardb.json +6 -0
- package/tests/fixtures/alibaba-maestro-routing/inputs/050-happy-tablestore-partition-key.json +7 -0
- package/tests/fixtures/alibaba-maestro-routing/inputs/adv-tablestore-not-polardb.json +7 -0
- package/tests/fixtures/alibaba-maestro-routing/taxonomy.json +13 -0
- package/tests/fixtures/aws-maestro-routing/expected/042-happy-dynamodb-patterns.json +6 -0
- package/tests/fixtures/aws-maestro-routing/expected/043-happy-dynamodb-vector-index.json +6 -0
- package/tests/fixtures/aws-maestro-routing/inputs/042-happy-dynamodb-patterns.json +7 -0
- package/tests/fixtures/aws-maestro-routing/inputs/043-happy-dynamodb-vector-index.json +7 -0
- package/tests/fixtures/aws-maestro-routing/taxonomy.json +15 -1
- package/tests/fixtures/azure-maestro-routing/expected/028-happy-cosmosdb-pattern-feature-plan.json +6 -0
- package/tests/fixtures/azure-maestro-routing/expected/029-happy-cosmosdb-pattern-refactor.json +6 -0
- package/tests/fixtures/azure-maestro-routing/expected/adv-cosmos-hot-partition-not-key-vault.json +6 -0
- package/tests/fixtures/azure-maestro-routing/expected/adv-cosmos-partition-key-not-key-vault.json +6 -0
- package/tests/fixtures/azure-maestro-routing/expected/adv-cosmos-throttling-investigation.json +6 -0
- package/tests/fixtures/azure-maestro-routing/inputs/028-happy-cosmosdb-pattern-feature-plan.json +7 -0
- package/tests/fixtures/azure-maestro-routing/inputs/029-happy-cosmosdb-pattern-refactor.json +7 -0
- package/tests/fixtures/azure-maestro-routing/inputs/adv-cosmos-hot-partition-not-key-vault.json +7 -0
- package/tests/fixtures/azure-maestro-routing/inputs/adv-cosmos-partition-key-not-key-vault.json +7 -0
- package/tests/fixtures/azure-maestro-routing/inputs/adv-cosmos-throttling-investigation.json +7 -0
- package/tests/fixtures/azure-maestro-routing/taxonomy.json +21 -2
- package/tests/fixtures/gcp-maestro-routing/expected/049-happy-bigtable-row-key.json +6 -0
- package/tests/fixtures/gcp-maestro-routing/expected/adv-bigtable-not-firestore.json +8 -0
- package/tests/fixtures/gcp-maestro-routing/inputs/049-happy-bigtable-row-key.json +7 -0
- package/tests/fixtures/gcp-maestro-routing/inputs/adv-bigtable-not-firestore.json +7 -0
- package/tests/fixtures/gcp-maestro-routing/taxonomy.json +15 -0
- package/tests/fixtures/huawei-maestro-routing/expected/050-happy-geminidb-cassandra-partition.json +6 -0
- package/tests/fixtures/huawei-maestro-routing/expected/adv-geminidb-mongo-routes-dds.json +7 -0
- package/tests/fixtures/huawei-maestro-routing/inputs/050-happy-geminidb-cassandra-partition.json +7 -0
- package/tests/fixtures/huawei-maestro-routing/inputs/adv-geminidb-mongo-routes-dds.json +7 -0
- package/tests/fixtures/huawei-maestro-routing/taxonomy.json +15 -0
- package/tests/fixtures/nosql-scenarios/scenarios.json +472 -0
- package/tests/fixtures/oci-maestro-routing/expected/031-happy-nosql-database-architect.json +6 -0
- package/tests/fixtures/oci-maestro-routing/expected/032-happy-nosql-global-active-table.json +6 -0
- package/tests/fixtures/oci-maestro-routing/expected/033-happy-nosql-pattern-recovery.json +6 -0
- package/tests/fixtures/oci-maestro-routing/expected/034-happy-nosql-pattern-refactor.json +6 -0
- package/tests/fixtures/oci-maestro-routing/expected/adv-nosql-live-mutation.json +6 -0
- package/tests/fixtures/oci-maestro-routing/expected/adv-nosql-not-autonomous.json +7 -0
- package/tests/fixtures/oci-maestro-routing/inputs/031-happy-nosql-database-architect.json +7 -0
- package/tests/fixtures/oci-maestro-routing/inputs/032-happy-nosql-global-active-table.json +7 -0
- package/tests/fixtures/oci-maestro-routing/inputs/033-happy-nosql-pattern-recovery.json +7 -0
- package/tests/fixtures/oci-maestro-routing/inputs/034-happy-nosql-pattern-refactor.json +7 -0
- package/tests/fixtures/oci-maestro-routing/inputs/adv-nosql-live-mutation.json +7 -0
- package/tests/fixtures/oci-maestro-routing/inputs/adv-nosql-not-autonomous.json +7 -0
- package/tests/fixtures/oci-maestro-routing/taxonomy.json +27 -0
- package/tests/requirements-ci.txt +8 -0
- package/tests/validate-aws-skill-quality.py +7 -0
- package/tests/validate-nosql-audit.py +741 -0
- package/tests/validate-nosql-operations.py +136 -0
- package/tests/validate-nosql-pattern-evals.py +96 -0
- package/tests/validate-nosql-scenarios.py +94 -0
- package/tests/validate-skill-manifest.py +6 -1
- package/tests/validate-skill-references.py +225 -0
|
@@ -0,0 +1,122 @@
|
|
|
1
|
+
# audit --mode live
|
|
2
|
+
|
|
3
|
+
Commands are examples for an operator holding read-only authorization; the skill
|
|
4
|
+
does not run them. They read Bigtable control-plane metadata only. Expectations come
|
|
5
|
+
from [the operations reference](../../operations.md).
|
|
6
|
+
|
|
7
|
+
## Before any command
|
|
8
|
+
|
|
9
|
+
- Confirm the approved principal, project, instance, clusters and tables. Stop on any
|
|
10
|
+
mismatch; never switch target to make a command work. Bigtable instance IDs and
|
|
11
|
+
cluster locations come from the approved scope, not from discovery.
|
|
12
|
+
- Use a read-only role. Write output to a private directory (`umask 077`). Never
|
|
13
|
+
print keys, connection strings or customer data. Do not read table rows.
|
|
14
|
+
|
|
15
|
+
Identity check, using the active account and the active configuration [BT-E901] [BT-E902]:
|
|
16
|
+
|
|
17
|
+
```bash
|
|
18
|
+
set -euo pipefail
|
|
19
|
+
: "${GCP_PROJECT:?Approved project ID}" "${BT_INSTANCE:?Approved instance ID}" \
|
|
20
|
+
"${BT_TABLE:?Approved table ID}" "${EXPECTED_ACCOUNT:?Approved principal}"
|
|
21
|
+
umask 077
|
|
22
|
+
audit_dir=$(mktemp -d)
|
|
23
|
+
gcloud auth list --filter=status:ACTIVE --format="value(account)" > "$audit_dir/account.txt"
|
|
24
|
+
gcloud config list --format=json > "$audit_dir/config.json"
|
|
25
|
+
grep -qxF "$EXPECTED_ACCOUNT" "$audit_dir/account.txt" || { echo "Principal mismatch; stop" >&2; exit 1; }
|
|
26
|
+
jq -e --arg p "$GCP_PROJECT" '.core.project == $p' "$audit_dir/config.json" >/dev/null \
|
|
27
|
+
|| { echo "Project mismatch; stop" >&2; exit 1; } # core/project property [BT-E902]
|
|
28
|
+
# Impersonation or an access-token file makes requests run as another identity [BT-E919] [BT-E920]
|
|
29
|
+
jq -e '(.auth.impersonate_service_account // "") == "" and (.auth.access_token_file // "") == ""' \
|
|
30
|
+
"$audit_dir/config.json" >/dev/null || { echo "Credential override set; stop" >&2; exit 1; }
|
|
31
|
+
```
|
|
32
|
+
|
|
33
|
+
The blocks below assume the variables and `audit_dir` from this block.
|
|
34
|
+
|
|
35
|
+
## Backup and restore
|
|
36
|
+
|
|
37
|
+
Backups on the approved instance, and the table's replication and schema metadata
|
|
38
|
+
[BT-E906] [BT-E907]:
|
|
39
|
+
|
|
40
|
+
```bash
|
|
41
|
+
gcloud bigtable backups list --instance="$BT_INSTANCE" --project="$GCP_PROJECT" --format=json > "$audit_dir/backups.json"
|
|
42
|
+
gcloud bigtable instances tables describe "$BT_TABLE" --instance="$BT_INSTANCE" --view=full --project="$GCP_PROJECT" --format=json > "$audit_dir/table.json"
|
|
43
|
+
```
|
|
44
|
+
|
|
45
|
+
## Disaster recovery and replication
|
|
46
|
+
|
|
47
|
+
Clusters (locations, state) and app profiles (routing policy) of the instance
|
|
48
|
+
[BT-E904] [BT-E905]:
|
|
49
|
+
|
|
50
|
+
```bash
|
|
51
|
+
gcloud bigtable clusters list --instances="$BT_INSTANCE" --project="$GCP_PROJECT" --format=json > "$audit_dir/clusters.json"
|
|
52
|
+
gcloud bigtable app-profiles list --instance="$BT_INSTANCE" --project="$GCP_PROJECT" --format=json > "$audit_dir/app-profiles.json"
|
|
53
|
+
```
|
|
54
|
+
|
|
55
|
+
## Cost
|
|
56
|
+
|
|
57
|
+
**No live command:** spend lives in Cloud Billing reports and the billing export,
|
|
58
|
+
not in the Bigtable resource API. Searched the gcloud Bigtable reference; no cost
|
|
59
|
+
command exists. Node counts and storage types come from `clusters.json` in the
|
|
60
|
+
section above, and spend needs the billing console or an approved billing export.
|
|
61
|
+
|
|
62
|
+
## Monitoring
|
|
63
|
+
|
|
64
|
+
Alerting policies in the project; filter for Bigtable metrics in the output [BT-E913]:
|
|
65
|
+
|
|
66
|
+
```bash
|
|
67
|
+
gcloud monitoring policies list --project="$GCP_PROJECT" --format=json > "$audit_dir/alert-policies.json"
|
|
68
|
+
```
|
|
69
|
+
|
|
70
|
+
## Performance
|
|
71
|
+
|
|
72
|
+
**No live command:** CPU, hot tablets and Key Visualizer data come from Cloud
|
|
73
|
+
Monitoring metrics and the Key Visualizer console, not from a gcloud Bigtable
|
|
74
|
+
command. Searched the gcloud Bigtable reference; none returns them. Use the
|
|
75
|
+
metrics views named in the operations reference with an approved Monitoring read.
|
|
76
|
+
|
|
77
|
+
## IAM
|
|
78
|
+
|
|
79
|
+
Instance, table and project policies [BT-E908] [BT-E909] [BT-E910]:
|
|
80
|
+
|
|
81
|
+
```bash
|
|
82
|
+
gcloud bigtable instances get-iam-policy "$BT_INSTANCE" --project="$GCP_PROJECT" --format=json > "$audit_dir/instance-iam.json"
|
|
83
|
+
gcloud bigtable instances tables get-iam-policy "$BT_TABLE" --instance="$BT_INSTANCE" --project="$GCP_PROJECT" --format=json > "$audit_dir/table-iam.json"
|
|
84
|
+
gcloud projects get-iam-policy "$GCP_PROJECT" --format=json > "$audit_dir/project-iam.json"
|
|
85
|
+
```
|
|
86
|
+
|
|
87
|
+
## Tagging
|
|
88
|
+
|
|
89
|
+
Tag bindings on the instance; set the parent to the instance's full resource name
|
|
90
|
+
from the approved scope [BT-E912] [BT-E903]:
|
|
91
|
+
|
|
92
|
+
```bash
|
|
93
|
+
: "${INSTANCE_FULL_RESOURCE_NAME:?Approved full resource name of the instance}"
|
|
94
|
+
gcloud resource-manager tags bindings list --parent="$INSTANCE_FULL_RESOURCE_NAME" --effective --format=json > "$audit_dir/tag-bindings.json"
|
|
95
|
+
gcloud bigtable instances describe "$BT_INSTANCE" --project="$GCP_PROJECT" --format=json > "$audit_dir/instance.json"
|
|
96
|
+
```
|
|
97
|
+
|
|
98
|
+
## Encryption
|
|
99
|
+
|
|
100
|
+
Cluster metadata carries the encryption configuration; the table `encryption` view
|
|
101
|
+
returns only the encryption-related fields [BT-E904] [BT-E907]:
|
|
102
|
+
|
|
103
|
+
```bash
|
|
104
|
+
gcloud bigtable clusters list --instances="$BT_INSTANCE" --project="$GCP_PROJECT" --format=json > "$audit_dir/clusters-encryption.json"
|
|
105
|
+
gcloud bigtable instances tables describe "$BT_TABLE" --instance="$BT_INSTANCE" --view=encryption --project="$GCP_PROJECT" --format=json > "$audit_dir/table-encryption.json"
|
|
106
|
+
```
|
|
107
|
+
|
|
108
|
+
## Network isolation
|
|
109
|
+
|
|
110
|
+
**No live command:** VPC Service Controls perimeters and Private Service Connect
|
|
111
|
+
endpoints belong to the Access Context Manager and VPC APIs, whose reference pages
|
|
112
|
+
were not retrieved in this pass. Bigtable has no per-instance public-endpoint
|
|
113
|
+
setting to read.
|
|
114
|
+
|
|
115
|
+
## Audit logging
|
|
116
|
+
|
|
117
|
+
Recent audit log entries for the Bigtable service; the format keeps only time,
|
|
118
|
+
method and caller, not request payloads [BT-E911]:
|
|
119
|
+
|
|
120
|
+
```bash
|
|
121
|
+
gcloud logging read 'protoPayload.serviceName="bigtable.googleapis.com"' --project="$GCP_PROJECT" --freshness=7d --limit=50 --format="value(timestamp,protoPayload.methodName,protoPayload.authenticationInfo.principalEmail)" > "$audit_dir/audit-log.txt"
|
|
122
|
+
```
|
|
@@ -0,0 +1,140 @@
|
|
|
1
|
+
# audit --mode offline
|
|
2
|
+
|
|
3
|
+
Inputs are the repository (IaC, application config, client code) and sanitized
|
|
4
|
+
exports supplied by the user. Use local tools only: no cloud CLI, network call,
|
|
5
|
+
credential or customer data. Field names follow the Bigtable Admin API resources
|
|
6
|
+
[BT-E914] [BT-E915] [BT-E916] [BT-E917] [BT-E918]. An absent setting in the
|
|
7
|
+
repository does not prove the live setting; record it as UNVERIFIED. Expectations
|
|
8
|
+
come from [the operations reference](../../operations.md).
|
|
9
|
+
|
|
10
|
+
## Backup and restore
|
|
11
|
+
|
|
12
|
+
- Check tables for an automated backup policy (`automatedBackupPolicy`) and compare
|
|
13
|
+
its retention with the recovery objective [BT-E916].
|
|
14
|
+
- Check any scheduled or on-demand backup tooling for expiry (`expireTime`) and for
|
|
15
|
+
`hotToStandardTime` if hot backups are used [BT-E918].
|
|
16
|
+
- Check the restore runbook: a restore creates a new table, and garbage collection
|
|
17
|
+
policies must be set before new writes (operations reference, Backup and restore).
|
|
18
|
+
- Check `deletionProtection` on production tables [BT-E916].
|
|
19
|
+
|
|
20
|
+
```bash
|
|
21
|
+
rg -n -i 'automated.?backup|expire.?time|hot.?to.?standard|deletion.?protection' \
|
|
22
|
+
--glob '*.tf' --glob '*.json' --glob '*.yaml' --glob '*.yml' --glob '*.md'
|
|
23
|
+
```
|
|
24
|
+
|
|
25
|
+
## Disaster recovery and replication
|
|
26
|
+
|
|
27
|
+
- Check how many clusters an instance defines and in which zones; replication needs
|
|
28
|
+
more than one cluster (operations reference, Disaster recovery and replication).
|
|
29
|
+
- Check app-profile routing: `multiClusterRoutingUseAny` versus `singleClusterRouting`
|
|
30
|
+
decides automatic versus manual failover [BT-E917].
|
|
31
|
+
- Check that code which needs single-row transactions does not run under a
|
|
32
|
+
multi-cluster routing profile (`allowTransactionalWrites` applies to single-cluster
|
|
33
|
+
routing) [BT-E917].
|
|
34
|
+
- Check cross-region recovery steps in the runbook against backup copies.
|
|
35
|
+
|
|
36
|
+
```bash
|
|
37
|
+
rg -n -i 'multi.?cluster.?routing|single.?cluster.?routing|allow.?transactional.?writes|app.?profile' \
|
|
38
|
+
--glob '*.tf' --glob '*.json' --glob '*.yaml' --glob '*.py' --glob '*.java' --glob '*.go'
|
|
39
|
+
```
|
|
40
|
+
|
|
41
|
+
## Cost
|
|
42
|
+
|
|
43
|
+
- Check autoscaling bounds (`clusterAutoscalingConfig`, `autoscalingLimits`,
|
|
44
|
+
`autoscalingTargets`) against fixed `serveNodes` [BT-E915].
|
|
45
|
+
- Check `defaultStorageType` (SSD or HDD) and replicated clusters, which each hold
|
|
46
|
+
their own storage copy (operations reference, Cost).
|
|
47
|
+
- Check backup retention and the number of scheduled copies for storage growth.
|
|
48
|
+
- Check data-access audit log enablement, which has a cost impact.
|
|
49
|
+
|
|
50
|
+
```bash
|
|
51
|
+
rg -n -i 'autoscaling|serve.?nodes|default.?storage.?type|node.?scaling.?factor' \
|
|
52
|
+
--glob '*.tf' --glob '*.json' --glob '*.yaml'
|
|
53
|
+
```
|
|
54
|
+
|
|
55
|
+
## Monitoring
|
|
56
|
+
|
|
57
|
+
- Check for alerting policies on storage utilization and CPU against the thresholds
|
|
58
|
+
in the operations reference (Monitoring, Performance).
|
|
59
|
+
- Check dashboards or IaC for hottest-node CPU, replication latency and error rate.
|
|
60
|
+
- Check that monitoring is defined in code, not only in the console.
|
|
61
|
+
|
|
62
|
+
```bash
|
|
63
|
+
rg -n -i 'storage_utilization|bigtable\.googleapis\.com/cluster|cpu_load|replication.?latency' \
|
|
64
|
+
--glob '*.tf' --glob '*.json' --glob '*.yaml'
|
|
65
|
+
```
|
|
66
|
+
|
|
67
|
+
## Performance
|
|
68
|
+
|
|
69
|
+
- Check row-key construction in client code for leading timestamps or sequential
|
|
70
|
+
IDs (operations reference, Performance; design guide).
|
|
71
|
+
- Check for read-modify-write or check-and-mutate calls that assume multi-row atomicity.
|
|
72
|
+
- Check `columnFamilies` garbage collection (`gcRule`) and max-version or max-age
|
|
73
|
+
settings [BT-E916].
|
|
74
|
+
- Check client connection reuse and warm-up code.
|
|
75
|
+
|
|
76
|
+
```bash
|
|
77
|
+
rg -n -i 'row.?key|gc.?rule|max.?versions|max.?age|ReadModifyWrite|CheckAndMutate' \
|
|
78
|
+
--glob '*.tf' --glob '*.py' --glob '*.java' --glob '*.go' --glob '*.ts'
|
|
79
|
+
```
|
|
80
|
+
|
|
81
|
+
## IAM
|
|
82
|
+
|
|
83
|
+
- Check role bindings for `roles/bigtable.admin` granted to applications; prefer
|
|
84
|
+
`roles/bigtable.user`, `roles/bigtable.reader` or `roles/bigtable.viewer` at
|
|
85
|
+
table level (operations reference, IAM).
|
|
86
|
+
- Check for `allUsers` or `allAuthenticatedUsers` members.
|
|
87
|
+
- Check for service-account key files committed to the repository.
|
|
88
|
+
- Check that no project-wide grant duplicates a narrower table-level grant.
|
|
89
|
+
|
|
90
|
+
```bash
|
|
91
|
+
rg -n -i 'roles/bigtable\.|allUsers|allAuthenticatedUsers|iam.?member|iam.?binding' \
|
|
92
|
+
--glob '*.tf' --glob '*.json' --glob '*.yaml'
|
|
93
|
+
```
|
|
94
|
+
|
|
95
|
+
## Tagging
|
|
96
|
+
|
|
97
|
+
- Check that instances carry resource tags (`tags`) where conditional IAM depends on
|
|
98
|
+
them, and labels (`labels`) for billing grouping [BT-E914].
|
|
99
|
+
- Check that tag keys and values are not secrets or customer data.
|
|
100
|
+
|
|
101
|
+
```bash
|
|
102
|
+
rg -n -i '\btags\b|\blabels\b|tag.?binding' --glob '*.tf' --glob '*.json' --glob '*.yaml'
|
|
103
|
+
```
|
|
104
|
+
|
|
105
|
+
## Encryption
|
|
106
|
+
|
|
107
|
+
- Check clusters for `encryptionConfig` with `kmsKeyName` when CMEK is required;
|
|
108
|
+
CMEK is set at cluster creation and is immutable (operations reference, Encryption)
|
|
109
|
+
[BT-E915].
|
|
110
|
+
- Check that the key region matches each cluster's region.
|
|
111
|
+
- Check that backup and restore destinations are CMEK-protected when the source is.
|
|
112
|
+
|
|
113
|
+
```bash
|
|
114
|
+
rg -n -i 'encryption.?config|kms.?key.?name|cmek' --glob '*.tf' --glob '*.json' --glob '*.yaml'
|
|
115
|
+
```
|
|
116
|
+
|
|
117
|
+
## Network isolation
|
|
118
|
+
|
|
119
|
+
- Check IaC for VPC Service Controls perimeters that include `bigtable.googleapis.com`
|
|
120
|
+
(operations reference, Network isolation).
|
|
121
|
+
- Check for Private Service Connect or Private Google Access configuration used by
|
|
122
|
+
clients.
|
|
123
|
+
- Check client config for hard-coded public endpoints.
|
|
124
|
+
|
|
125
|
+
```bash
|
|
126
|
+
rg -n -i 'bigtable\.googleapis\.com|bigtableadmin\.googleapis\.com|service.?perimeter|private.?google.?access|psc' \
|
|
127
|
+
--glob '*.tf' --glob '*.json' --glob '*.yaml'
|
|
128
|
+
```
|
|
129
|
+
|
|
130
|
+
## Audit logging
|
|
131
|
+
|
|
132
|
+
- Check that Data Access audit logs are configured for `bigtable.googleapis.com`
|
|
133
|
+
(DATA_READ, DATA_WRITE, ADMIN_READ) as well as the default Admin Activity logs
|
|
134
|
+
(operations reference, Audit logging).
|
|
135
|
+
- Check for log sinks or retention that carry those logs, and for exempted principals.
|
|
136
|
+
|
|
137
|
+
```bash
|
|
138
|
+
rg -n -i 'audit.?config|log.?type|DATA_READ|DATA_WRITE|ADMIN_READ|exempted.?members' \
|
|
139
|
+
--glob '*.tf' --glob '*.json' --glob '*.yaml'
|
|
140
|
+
```
|
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
# audit
|
|
2
|
+
|
|
3
|
+
Load only for an audit request. Offline is the default. After reading this file,
|
|
4
|
+
load **only** the selected variant: [offline](audit/offline.md) or
|
|
5
|
+
[live](audit/live.md). Do not read both.
|
|
6
|
+
|
|
7
|
+
## Scope
|
|
8
|
+
|
|
9
|
+
- Name the project, instance, clusters, tables and the selected sections of
|
|
10
|
+
[the operations reference](../operations.md). Unselected sections are out of scope.
|
|
11
|
+
- An audit is a technical risk review, not a compliance attestation.
|
|
12
|
+
|
|
13
|
+
## Findings
|
|
14
|
+
|
|
15
|
+
For each finding give: severity, section, evidence (file:line, or sanitized command
|
|
16
|
+
output with its retrieval time), the expectation from the operations reference with
|
|
17
|
+
its evidence ID, impact, the smallest proposed fix and how to verify it.
|
|
18
|
+
|
|
19
|
+
- PASS only for a check actually performed. Missing evidence is UNVERIFIED.
|
|
20
|
+
- An absent repository setting does not prove the live setting is off.
|
|
21
|
+
- Propose fixes; never apply them as part of the audit.
|
|
@@ -0,0 +1,83 @@
|
|
|
1
|
+
# Evidence ledger — Cloud Bigtable
|
|
2
|
+
|
|
3
|
+
Every material claim in
|
|
4
|
+
[bigtable-design-guide.md](bigtable-design-guide.md) cites one row below as
|
|
5
|
+
`[BT-Exx]`. `tests/validate-skill-references.py` fails the build if a citation
|
|
6
|
+
has no row, a row is never cited, or a source is not an allow-listed Google
|
|
7
|
+
documentation host.
|
|
8
|
+
|
|
9
|
+
Scope: **Cloud Bigtable**. Not Firestore, Spanner or self-managed HBase.
|
|
10
|
+
`VERIFIED` = the section was retrieved on the retrieval date and supports the
|
|
11
|
+
claim as worded; it is documentation verification, not a behavioral test.
|
|
12
|
+
Limits change: re-fetch before relying on a number.
|
|
13
|
+
|
|
14
|
+
| ID | Claim | Source | Section | Retrieved | Status |
|
|
15
|
+
| --- | --- | --- | --- | --- | --- |
|
|
16
|
+
| BT-E01 | Each table is a sorted key-value map; only one value per row, the row key, is indexed; related columns are grouped into column families; each cell holds a uniquely timestamped version; tables are sparse. | <https://docs.cloud.google.com/bigtable/docs/overview> | Bigtable storage model | 2026-11-08 | VERIFIED |
|
|
17
|
+
| BT-E02 | Row keys sort lexicographically (big-endian byte order), so numbers need padding to sort numerically; well-planned prefixes keep related data in contiguous rows. | <https://docs.cloud.google.com/bigtable/docs/schema-design> | Row keys | 2026-11-08 | VERIFIED |
|
|
18
|
+
| BT-E03 | Row keys to avoid: keys starting with a timestamp (sequential writes hotspot a single node), sequential numeric IDs (reverse them instead), and hashed values (they destroy the natural sort order and hamper Key Visualizer). | <https://docs.cloud.google.com/bigtable/docs/schema-design> | Row keys to avoid | 2026-11-08 | VERIFIED |
|
|
19
|
+
| BT-E04 | For time-based data, never put a timestamp alone or first in the row key; combine an entity identifier with the timestamp, and consider reversed timestamps for newest-first reads, still not at the start of the key. | <https://docs.cloud.google.com/bigtable/docs/schema-design> | Time-based data | 2026-11-08 | VERIFIED |
|
|
20
|
+
| BT-E05 | Mutations are always atomic at the row level, including multi-column mutations in one operation; Bigtable does not support transactions that atomically update more than one row; read-modify-write and check-and-mutate are single-row transactions. | <https://docs.cloud.google.com/bigtable/docs/routing> | Single-row transactions | 2026-11-08 | VERIFIED |
|
|
21
|
+
| BT-E06 | Single-row transactions cannot be enabled with multi-cluster routing because they can cause data conflicts; multi-cluster routing is the choice for high availability. | <https://docs.cloud.google.com/bigtable/docs/routing> | Routing options | 2026-11-08 | VERIFIED |
|
|
22
|
+
| BT-E07 | A standard app profile sets the routing policy and whether single-row transactions are allowed; the default profile is single-cluster with transactions enabled if the instance was created with 1 cluster, and multi-cluster without transactions if created with 2 or more; the default profile does not change when clusters are added or removed. | <https://docs.cloud.google.com/bigtable/docs/app-profiles> | Standard app profiles | 2026-11-08 | VERIFIED |
|
|
23
|
+
| BT-E08 | Replication is eventually consistent by default, typically seconds to minutes but potentially longer under load or distance; read-your-writes is achieved with single-cluster routing (all app profiles on the same cluster), and a high rate of read-your-writes with multi-cluster row-affinity routing or clusters each in a different region; strong consistency additionally requires not using the other clusters except for failover; multi-cluster routing across regions gives read-your-writes within the source region unless failover occurs. | <https://docs.cloud.google.com/bigtable/docs/replication-overview> | Consistency model | 2026-11-08 | VERIFIED |
|
|
24
|
+
| BT-E09 | Garbage collection runs asynchronously during compaction, typically within a few days but up to a week, timing cannot be changed, and data appears in reads until deleted; rules are max age, max versions, or intersection/union/nested combinations; always apply a read filter matching the GC rules. | <https://docs.cloud.google.com/bigtable/docs/garbage-collection> | Garbage collection overview | 2026-11-08 | VERIFIED |
|
|
25
|
+
| BT-E10 | Recommended limits: 100 column families per table, 16 KB per column qualifier, 10 MB per cell, 100 MB per row. Hard limits: 4 KB per row key, 100 MB per cell, 256 MB per row, 200 MB per mutation. At most 1,000 tables per instance. Storage per node: 5 TB on SSD without tiered storage, 32 TB (Enterprise) or 64 TB (Enterprise Plus) on SSD with tiered storage of which at most 5 TB is SSD, and 16 TB on HDD, using at most 70% as a best practice. Backup retention: minimum 6 hours, maximum 90 days (Enterprise) or 365 days (Enterprise Plus). | <https://docs.cloud.google.com/bigtable/quotas> | Recommended limits; Hard limits; Storage per node; Backups | 2026-11-08 | VERIFIED |
|
|
26
|
+
| BT-E11 | SSD or HDD storage is chosen at instance creation and is permanent; to move a table to the other storage type, back it up and restore it to a new table in an instance that uses that storage type. | <https://docs.cloud.google.com/bigtable/docs/choosing-ssd-hdd> | Choose between SSD and HDD storage | 2026-11-08 | VERIFIED |
|
|
27
|
+
| BT-E12 | Autoscaling: CPU utilization target 10-80%; minimum nodes at least 10% of maximum and maximum at most 10x minimum (hard limits); storage utilization target defaults to 50% (2.5 TB SSD, 8 TB HDD per node); with 2x node scaling (the Enterprise Plus default) minimum and maximum nodes must be even. | <https://docs.cloud.google.com/bigtable/docs/autoscaling> | Autoscaling parameters | 2026-11-08 | VERIFIED |
|
|
28
|
+
| BT-E13 | Predefined roles: `roles/bigtable.admin` (all instances including data, can create instances), `roles/bigtable.user` (read-write data access), `roles/bigtable.reader` (read-only data access), `roles/bigtable.viewer` (no data access); data roles can be granted as low as the table. | <https://docs.cloud.google.com/bigtable/docs/access-control> | Predefined roles | 2026-11-08 | VERIFIED |
|
|
29
|
+
| BT-E14 | Automated backup keeps backups 7 days by default; restores always create a new table, then requests are re-routed to it; restoring into a replicated instance incurs a one-time replication cost, restoring into an instance that shares no region with the backup's instance incurs standard network rates, and copying a backup to another region is billed at network rates. | <https://docs.cloud.google.com/bigtable/docs/backups> | Retention; Restoration strategy; Pricing | 2026-11-08 | VERIFIED |
|
|
30
|
+
| BT-E15 | Client libraries: Go `cloud.google.com/go/bigtable`; Java Maven `com.google.cloud:google-cloud-bigtable`; Node.js `@google-cloud/bigtable`; Python `google-cloud-bigtable`; C# `Google.Cloud.Bigtable.V2` (installed with `-Pre`); HBase client for Java under `com.google.cloud.bigtable` (`bigtable-hbase-1.x`, `bigtable-hbase-1.x-hadoop`, `bigtable-hbase-1.x-shaded`; 2.x versions also exist and add an HBase async client); authentication uses Application Default Credentials. | <https://docs.cloud.google.com/bigtable/docs/reference/libraries> | Install the client library | 2026-11-08 | VERIFIED |
|
|
31
|
+
| BT-E16 | Pricing and per-node throughput figures were not retrieved in this pass. | <https://cloud.google.com/bigtable/pricing> | Pricing | 2026-11-08 | UNVERIFIED |
|
|
32
|
+
| BT-E17 | Continuous materialized views can serve as asynchronous secondary indexes: a subset of source columns with a different row key that must include the source row key; applications do not write to them, and Bigtable synchronizes them with the source table with eventual consistency. | <https://docs.cloud.google.com/bigtable/docs/asynchronous-secondary-index> | Create an asynchronous secondary index | 2026-11-08 | VERIFIED |
|
|
33
|
+
| BT-E101 | Hot backups (production-ready, optimized for fast restoration) can be created on demand or by automated policy only for tables in SSD instances, not HDD and not tiered-storage tables; a hot backup converts to standard but not the reverse; a backup copy is always a standard backup and a copy of a copy cannot be made. | <https://docs.cloud.google.com/bigtable/docs/backups> | Hot backups: "You can create on-demand hot backups and configure hot automated backups only" | 2026-11-08 | VERIFIED |
|
|
34
|
+
| BT-E102 | A restore creates a new table; the restored table does not inherit the source table's garbage collection policies, which must be configured before new writes. | <https://docs.cloud.google.com/bigtable/docs/backups> | Restoration: "A new table restored from a backup doesn't inherit the garbage collection" | 2026-11-08 | VERIFIED |
|
|
35
|
+
| BT-E103 | A backup is the table state on the single cluster that stores it; data not yet replicated to that cluster from other clusters is not included. Manual backups are stored on one chosen cluster; automated backup creates a daily backup on each cluster. | <https://docs.cloud.google.com/bigtable/docs/backups> | Replication and backing up: "Table data that has not yet been replicated from another cluster in the instance is not included in the backup." | 2026-11-08 | VERIFIED |
|
|
36
|
+
| BT-E104 | Automated backup policy retention is configurable up to 90 days in both editions (default 7 days); on-demand backups up to 90 days (Enterprise) or 365 days (Enterprise Plus); a backup copy has a maximum retention of 30 days; up to 150 backups per table per cluster; a cluster holding backups cannot be deleted. | <https://docs.cloud.google.com/bigtable/docs/backups> | Retention: "You can configure a custom retention period for an automated backup policy" | 2026-11-08 | VERIFIED |
|
|
37
|
+
| BT-E105 | Backup operations (create, copy, restore) are not charged; backup storage is billed (standard incrementally, hot as the full logical copy), cross-region copy and cross-region restore incur standard network rates, and restoring into a replicated instance incurs a one-time replication cost. | <https://docs.cloud.google.com/bigtable/docs/backups> | Costs: "You are not charged for backup operations, including creating, copying, or restoring from a backup." | 2026-11-08 | VERIFIED |
|
|
38
|
+
| BT-E106 | A backup in a CMEK-protected cluster is pinned to the primary key version at creation; the pinned version must be enabled to restore, and restoring to a different instance requires the destination instance to be CMEK-protected. | <https://docs.cloud.google.com/bigtable/docs/backups> | CMEK: "If you want to restore from a CMEK-protected backup to" | 2026-11-08 | VERIFIED |
|
|
39
|
+
| BT-E107 | Replication copies data across multiple zones or regions within an instance; an instance can have clusters in up to 8 regions with at most one cluster per zone; Bigtable keeps a separate copy of the data in each cluster. | <https://docs.cloud.google.com/bigtable/docs/replication-overview> | Replication overview: "Bigtable instances can have clusters located in up to" | 2026-11-08 | VERIFIED |
|
|
40
|
+
| BT-E108 | With single-cluster routing failover is manual and based on the operator's judgement; with multi-cluster routing Bigtable fails over automatically to the nearest available cluster, even for very short unavailability. After failover reads can be stale until replication completes. | <https://docs.cloud.google.com/bigtable/docs/failovers> | Automatic failovers: "If an app profile uses multi-cluster routing, Bigtable handles" | 2026-11-08 | VERIFIED |
|
|
41
|
+
| BT-E109 | Conflicting writes to the same cell version on different clusters are resolved deterministically by last write wins on server-side time. | <https://docs.cloud.google.com/bigtable/docs/replication-overview> | Conflict resolution: "resolves the conflict using an internal last write wins algorithm based on the server-side" | 2026-11-08 | VERIFIED |
|
|
42
|
+
| BT-E110 | Bigtable bills for the instance type and total node count, storage used by tables and backups, and network bandwidth; storage and bandwidth are measured in GiB and accrue daily. | <https://cloud.google.com/bigtable/pricing> | Pricing: "The type of Bigtable instance and the total number of nodes in your instance's clusters." | 2026-11-08 | VERIFIED |
|
|
43
|
+
| BT-E111 | Nodes are billed hourly on the maximum node count in that hour with a one-hour minimum per node; multi-cluster instances are billed for every copy of the data; cross-region replication writes are billed at network rates. | <https://cloud.google.com/bigtable/pricing> | Pricing: "You are charged each hour for the maximum number of nodes that exist during that hour, multiplied by the hourly rate." | 2026-11-08 | VERIFIED |
|
|
44
|
+
| BT-E112 | Data Boost is an on-demand serverless compute option billed in SPU-seconds (about 1/1000th of a node per SPU) with a 60 SPU-second minimum per request and no additional storage or networking fees. | <https://cloud.google.com/bigtable/pricing> | Data Boost serverless compute: "You are charged for the SPU-seconds that you consume, with a minimum of at least 60 SPU-seconds per request." | 2026-11-08 | VERIFIED |
|
|
45
|
+
| BT-E113 | Backup storage is billed from creation until deletion, as standard (incremental) or hot backup storage; tiered storage moving data from SSD to the infrequent access tier is billed on the table_compaction SKU. | <https://cloud.google.com/bigtable/pricing> | Backups: "You are billed only for the backup storage that you use, and a backup can never be larger than the original table." | 2026-11-08 | VERIFIED |
|
|
46
|
+
| BT-E114 | Bigtable exports metrics to Cloud Monitoring; the documented alert uses metric type bigtable.googleapis.com/cluster/storage_utilization on the Cloud Bigtable Cluster resource with a threshold such as 70%. | <https://docs.cloud.google.com/bigtable/docs/monitoring-instance> | Create a storage utilization alert: "In the Metrics menu, select Storage utilization. (The metric.type is bigtable.googleapis.com/cluster/storage_utilization)." | 2026-11-08 | VERIFIED |
|
|
47
|
+
| BT-E115 | Console and Cloud Monitoring API metrics include average CPU utilization, CPU utilization of the hottest node, CPU by app profile/method/table, storage utilization, replication latency, system error rate, and read/write latency; cluster CPU or disk over thresholds degrades performance and can return errors. | <https://docs.cloud.google.com/bigtable/docs/monitoring-instance> | Understand resource usage: "The average CPU utilization across all nodes in the cluster. Includes change stream activity if a" | 2026-11-08 | VERIFIED |
|
|
48
|
+
| BT-E116 | If any cluster exceeds the per-node storage hard limit, writes to all clusters in the instance fail until nodes are added; the guidance is to stay under 70% of the hard limit. | <https://docs.cloud.google.com/bigtable/docs/monitoring-instance> | Storage utilization: "writes to all clusters in that instance will fail until you" | 2026-11-08 | VERIFIED |
|
|
49
|
+
| BT-E117 | Autoscaling is recommended; for manual allocation keep CPU utilization below 90% when optimizing for throughput and below 60% when optimizing for latency. | <https://docs.cloud.google.com/bigtable/docs/performance> | CPU utilization: "you must monitor the cluster's CPU utilization with the goal of keeping CPU" | 2026-11-08 | VERIFIED |
|
|
50
|
+
| BT-E118 | Tables are sharded into tablets assigned to nodes and rebalanced by access pattern; a hot tablet uses a disproportionate share of node CPU and can cause latency and replication delays, most often from hotspots on nearby rows; up to 50 hot tablets per cluster are listed. | <https://docs.cloud.google.com/bigtable/docs/hot-tablets> | Understand hot tablets: "A hot tablet is a tablet that exhibits overutilization of the node CPU" | 2026-11-08 | VERIFIED |
|
|
51
|
+
| BT-E119 | Poor schema design that concentrates traffic causes hotspots that can affect other tables in the same instance; reading many non-contiguous row keys in one request lacks parallelism and raises latency. | <https://docs.cloud.google.com/bigtable/docs/performance> | Reasons for slower performance: "in one table can affect the performance of other tables in the same instance." | 2026-11-08 | VERIFIED |
|
|
52
|
+
| BT-E120 | Cold starts and low QPS can increase latency; mitigations include low-rate artificial traffic and warming connections at client initialization. | <https://docs.cloud.google.com/bigtable/docs/performance> | Cold starts and low QPS: "Cold starts and low QPS can increase latency. Bigtable performs" | 2026-11-08 | VERIFIED |
|
|
53
|
+
| BT-E121 | IAM is the access control mechanism, applied on project, instance, cluster, table, backup, authorized view and continuous materialized view levels with downward policy inheritance; allUsers and allAuthenticatedUsers cannot be granted. | <https://docs.cloud.google.com/bigtable/docs/access-control> | Access control overview: "If you have permissions at a level, then you automatically have permissions" | 2026-11-08 | VERIFIED |
|
|
54
|
+
| BT-E122 | Permissions can be scoped at table level (write without read), backup level (prevent delete or restore), and authorized view level (read a view but not modify, or one of several views). | <https://docs.cloud.google.com/bigtable/docs/access-control> | Access control examples: "Allow a user to write to a table but not read from the table." | 2026-11-08 | VERIFIED |
|
|
55
|
+
| BT-E123 | Tags (key-value pairs bound to Google Cloud resources) can be used in conditional allow/deny and IAM policies; Bigtable instances can be tagged (requires roles/bigtable.admin to attach); instances are global resources and labels group instances for automation and billing. | <https://docs.cloud.google.com/bigtable/docs/tags> | About tags: "To attach tags to Bigtable instances, you need the" | 2026-11-08 | VERIFIED |
|
|
56
|
+
| BT-E124 | Bigtable encrypts customer content at rest by default (Google default encryption); CMEK via Cloud KMS (including Autokey) is optional, uses envelope encryption with the CMEK as key encryption key, and applies per cluster with a key in the cluster's region. | <https://docs.cloud.google.com/bigtable/docs/cmek> | CMEK: "By default, Bigtable encrypts customer content at rest." | 2026-11-08 | VERIFIED |
|
|
57
|
+
| BT-E125 | CMEK is configured only at cluster level (not backups, tables or app profiles); encryption configuration is immutable and instances cannot be converted between default encryption and CMEK; resources whose key is inaccessible for more than 30 consecutive days are automatically deleted. | <https://docs.cloud.google.com/bigtable/docs/cmek> | Limitations: "CMEK can only be configured at the cluster level. You cannot configure" | 2026-11-08 | VERIFIED |
|
|
58
|
+
| BT-E126 | If a key is disabled or destroyed Bigtable disables clusters in a cascade across the instance, which can take hours; the recommendation is to disable the keys of all clusters at the same time. | <https://docs.cloud.google.com/bigtable/docs/cmek> | Key disable behavior: "Key Point: Always disable the keys for every cluster in the instance at the same" | 2026-11-08 | VERIFIED |
|
|
59
|
+
| BT-E127 | Some data stays under Google default encryption and not the CMEK key: a subset of row keys marking range boundaries for routing, debugging data, data in transit or in memory, and a subset of timestamp values used for garbage collection. | <https://docs.cloud.google.com/bigtable/docs/cmek> | Data not protected by CMEK: "Some data is protected by Google default encryption at rest and not by the CMEK" | 2026-11-08 | VERIFIED |
|
|
60
|
+
| BT-E128 | Bigtable is GA in VPC Service Controls and perimeters can protect it; bigtable.googleapis.com and bigtableadmin.googleapis.com are bundled, so restricting the former restricts the latter; no known limitations. | <https://docs.cloud.google.com/vpc-service-controls/docs/supported-products> | Bigtable: "The Bigtable integration with VPC Service Controls has no known limitations." | 2026-11-08 | VERIFIED |
|
|
61
|
+
| BT-E129 | Private Service Connect backends support the global Bigtable APIs bigtable.googleapis.com and bigtableadmin.googleapis.com. | <https://docs.cloud.google.com/vpc/docs/private-service-connect-compatibility> | Backends and global Google APIs: "to a single supported global Google API. The following APIs are supported:" | 2026-11-08 | VERIFIED |
|
|
62
|
+
| BT-E130 | Private Google Access gives hosts with private IP addresses private connectivity to Google APIs and can be combined with a VPC Service Controls perimeter; restricted.googleapis.com is recommended when unsupported APIs are not needed. | <https://docs.cloud.google.com/vpc-service-controls/docs/private-connectivity> | Private Google Access with VPC Service Controls: "Private Google Access offers private connectivity for hosts in either a VPC network or an on-premises network" | 2026-11-08 | VERIFIED |
|
|
63
|
+
| BT-E131 | Bigtable methods requiring DATA_READ, DATA_WRITE or ADMIN_READ permissions generate Data Access audit logs; methods requiring ADMIN_WRITE generate Admin Activity audit logs; Bigtable service name is bigtable.googleapis.com and the page directs readers to enable Data Access audit logging and read the cost guidance first. | <https://docs.cloud.google.com/bigtable/docs/audit-logging> | Methods by permission type: "Methods that require an IAM permission with the type property value of DATA_READ, DATA_WRITE, or ADMIN_READ generate" | 2026-11-08 | VERIFIED |
|
|
64
|
+
| BT-E901 | gcloud auth list is a read-only listing of credentialed accounts and shows which is active (identity check). | <https://docs.cloud.google.com/sdk/gcloud/reference/auth/list> | NAME: "gcloud auth list - lists credentialed accounts" | 2026-11-09 | VERIFIED |
|
|
65
|
+
| BT-E902 | gcloud config list shows the active configuration properties, including account and project (identity check). | <https://docs.cloud.google.com/sdk/gcloud/reference/config/list> | NAME: "gcloud config list - list Google Cloud CLI properties for the currently active configuration" | 2026-11-09 | VERIFIED |
|
|
66
|
+
| BT-E903 | gcloud bigtable instances describe INSTANCE reads one instance's metadata. | <https://docs.cloud.google.com/sdk/gcloud/reference/bigtable/instances/describe> | NAME: "gcloud bigtable instances describe - describe an existing Bigtable instance" | 2026-11-09 | VERIFIED |
|
|
67
|
+
| BT-E904 | gcloud bigtable clusters list --instances lists the clusters of the named instances. | <https://docs.cloud.google.com/sdk/gcloud/reference/bigtable/clusters/list> | NAME: "gcloud bigtable clusters list - list existing Bigtable clusters" | 2026-11-09 | VERIFIED |
|
|
68
|
+
| BT-E905 | gcloud bigtable app-profiles list --instance lists the app profiles of an instance. | <https://docs.cloud.google.com/sdk/gcloud/reference/bigtable/app-profiles/list> | NAME: "gcloud bigtable app-profiles list - list Bigtable app profiles" | 2026-11-09 | VERIFIED |
|
|
69
|
+
| BT-E906 | gcloud bigtable backups list takes optional --instance and --cluster and lists backups. | <https://docs.cloud.google.com/sdk/gcloud/reference/bigtable/backups/list> | NAME: "gcloud bigtable backups list - list existing Bigtable backups" | 2026-11-09 | VERIFIED |
|
|
70
|
+
| BT-E907 | gcloud bigtable instances tables describe TABLE --instance reads table metadata; --view selects encryption, full, name, replication or schema. | <https://docs.cloud.google.com/sdk/gcloud/reference/bigtable/instances/tables/describe> | NAME: "gcloud bigtable instances tables describe - retrieve information about a table" | 2026-11-09 | VERIFIED |
|
|
71
|
+
| BT-E908 | gcloud bigtable instances get-iam-policy INSTANCE reads an instance IAM policy. | <https://docs.cloud.google.com/sdk/gcloud/reference/bigtable/instances/get-iam-policy> | NAME: "gcloud bigtable instances get-iam-policy - get the IAM policy for a Cloud Bigtable instance" | 2026-11-09 | VERIFIED |
|
|
72
|
+
| BT-E909 | gcloud bigtable instances tables get-iam-policy TABLE --instance reads a table IAM policy. | <https://docs.cloud.google.com/sdk/gcloud/reference/bigtable/instances/tables/get-iam-policy> | NAME: "gcloud bigtable instances tables get-iam-policy - get an IAM policy on a Cloud Bigtable table" | 2026-11-09 | VERIFIED |
|
|
73
|
+
| BT-E910 | gcloud projects get-iam-policy reads a project's IAM policy. | <https://docs.cloud.google.com/sdk/gcloud/reference/projects/get-iam-policy> | NAME: "gcloud projects get-iam-policy - get IAM policy for a project" | 2026-11-09 | VERIFIED |
|
|
74
|
+
| BT-E911 | gcloud logging read reads log entries with a filter, --freshness, --limit and --project flags, for audit-log evidence. | <https://docs.cloud.google.com/sdk/gcloud/reference/logging/read> | DESCRIPTION: "gcloud logging read reads log entries. Log entries matching log-filter are returned in order of decreasing timestamps" | 2026-11-09 | VERIFIED |
|
|
75
|
+
| BT-E912 | gcloud resource-manager tags bindings list --parent lists tag bindings on a full resource name; --effective shows inherited bindings. | <https://docs.cloud.google.com/sdk/gcloud/reference/resource-manager/tags/bindings/list> | NAME: "gcloud resource-manager tags bindings list - lists TagBindings bound to the specified resource" | 2026-11-09 | VERIFIED |
|
|
76
|
+
| BT-E913 | gcloud monitoring policies list lists alerting policies in the active project. | <https://docs.cloud.google.com/sdk/gcloud/reference/monitoring/policies/list> | NAME: "gcloud monitoring policies list - list alerting policies" | 2026-11-09 | VERIFIED |
|
|
77
|
+
| BT-E914 | Bigtable Admin API Instance resource has a tags map and a labels map. | <https://docs.cloud.google.com/bigtable/docs/reference/admin/rest/v2/projects.instances> | Fields: "Tag keys/values directly bound to this resource." | 2026-11-09 | VERIFIED |
|
|
78
|
+
| BT-E915 | Bigtable Admin API Cluster resource has encryptionConfig (CMEK), clusterConfig with clusterAutoscalingConfig, serveNodes and defaultStorageType. | <https://docs.cloud.google.com/bigtable/docs/reference/admin/rest/v2/projects.instances.clusters> | Fields: "The encryption configuration for CMEK-protected clusters." | 2026-11-09 | VERIFIED |
|
|
79
|
+
| BT-E916 | Bigtable Admin API Table resource has automatedBackupPolicy, changeStreamConfig, deletionProtection, columnFamilies and gcRule. | <https://docs.cloud.google.com/bigtable/docs/reference/admin/rest/v2/projects.instances.tables> | Fields: "If specified, automated backups are enabled for this table." | 2026-11-09 | VERIFIED |
|
|
80
|
+
| BT-E917 | Bigtable Admin API AppProfile resource has multiClusterRoutingUseAny or singleClusterRouting, plus standardIsolation or dataBoostIsolationReadOnly, and priority. | <https://docs.cloud.google.com/bigtable/docs/reference/admin/rest/v2/projects.instances.appProfiles> | Fields: "The standard options used for isolating this app profile's traffic from other use cases." | 2026-11-09 | VERIFIED |
|
|
81
|
+
| BT-E918 | Bigtable Admin API Backup resource has backupType, expireTime and hotToStandardTime. | <https://docs.cloud.google.com/bigtable/docs/reference/admin/rest/v2/projects.instances.clusters.backups> | Fields: "The time at which the hot backup will be converted to a standard backup." | 2026-11-09 | VERIFIED |
|
|
82
|
+
| BT-E919 | The gcloud auth/impersonate_service_account property makes API requests run as another service account instead of the active account. | <https://docs.cloud.google.com/sdk/gcloud/reference/topic/configurations> | auth, impersonate_service_account: "While set, all API requests will be made as the given service account or target service account in an impersonation delegation chain instead of the currently selected account." | 2026-11-11 | VERIFIED |
|
|
83
|
+
| BT-E920 | The gcloud auth/access_token_file property authenticates with an access token and ignores the active account's credentials. | <https://docs.cloud.google.com/sdk/gcloud/reference/topic/configurations> | auth, access_token_file: "Use this property to authenticate gcloud with an access token. The credentials of the active account (if it exists) will be ignored." | 2026-11-11 | VERIFIED |
|
|
@@ -0,0 +1,111 @@
|
|
|
1
|
+
# Cloud Bigtable operations
|
|
2
|
+
|
|
3
|
+
Operational coverage for Cloud Bigtable (Enterprise and Enterprise Plus editions, Data and Admin APIs). Every section uses the
|
|
4
|
+
same heading and states one status. Cite evidence rows from
|
|
5
|
+
[the evidence ledger](evidence-ledger.md) as `[BT-Exx]`.
|
|
6
|
+
`tests/validate-nosql-operations.py` enforces this structure.
|
|
7
|
+
|
|
8
|
+
Statuses:
|
|
9
|
+
|
|
10
|
+
- `VERIFIED`: the provider documents the capability; every statement below cites a
|
|
11
|
+
VERIFIED row.
|
|
12
|
+
- `PARTIAL`: some of it is documented and some is not, or it is limited (by tier,
|
|
13
|
+
mode, Region or API); say which part is which.
|
|
14
|
+
- `UNSUPPORTED`: provider documentation states the capability does not exist. Cite it.
|
|
15
|
+
- `UNVERIFIED`: no official page settled it in this pass. Say what was searched.
|
|
16
|
+
- `NOT APPLICABLE`: the capability does not apply to this service. Say why.
|
|
17
|
+
|
|
18
|
+
## Backup and restore
|
|
19
|
+
|
|
20
|
+
**Status:** VERIFIED
|
|
21
|
+
|
|
22
|
+
- Backups are per table and stored on one cluster; automated backup creates a daily backup on each cluster, default retention 7 days, up to 90 days for an automated policy; on-demand backups keep up to 90 days (Enterprise) or 365 days (Enterprise Plus); copies keep at most 30 days; up to 150 backups per table per cluster [BT-E14] [BT-E104] [BT-E103].
|
|
23
|
+
- Restore always creates a new table (never in place) and then requests are re-routed to it; the backup remains after restore [BT-E14].
|
|
24
|
+
- Hot backups (SSD instances only, not tiered-storage tables) speed up restoration; a hot backup can become standard but not the reverse; a copy is always a standard backup and a copy of a copy is not possible [BT-E101].
|
|
25
|
+
- Not restored: the new table does not inherit the source table's garbage collection policies, so set them before new writes [BT-E102]. A backup also excludes data not yet replicated to its cluster [BT-E103].
|
|
26
|
+
- CMEK-protected backups are pinned to the key version at creation; that version must be enabled to restore, and the destination instance must be CMEK-protected [BT-E106].
|
|
27
|
+
- Backups cannot be configured as CMEK resources separately from their cluster (see Encryption) [BT-E125].
|
|
28
|
+
|
|
29
|
+
## Disaster recovery and replication
|
|
30
|
+
|
|
31
|
+
**Status:** PARTIAL
|
|
32
|
+
|
|
33
|
+
- Replication keeps a separate copy of data in each cluster; an instance can span up to 8 regions with at most one cluster per zone [BT-E107].
|
|
34
|
+
- Failover is manual with single-cluster routing and automatic with multi-cluster routing to the nearest available cluster [BT-E108] [BT-E06].
|
|
35
|
+
- Replication is eventually consistent (typically seconds to minutes) and reads can be stale after failover until replication completes; conflicts resolve by last write wins [BT-E08] [BT-E109].
|
|
36
|
+
- Single-row transactions cannot be used with multi-cluster routing, which is the high-availability choice [BT-E06].
|
|
37
|
+
- Cross-region recovery from backup copies is documented [BT-E14].
|
|
38
|
+
- Not settled: no numeric RPO or RTO was found on the replication, failover or backup pages retrieved; the SLA page (cloud.google.com/bigtable/sla) was not cited, so no availability figure is stated here.
|
|
39
|
+
|
|
40
|
+
## Cost
|
|
41
|
+
|
|
42
|
+
**Status:** VERIFIED
|
|
43
|
+
|
|
44
|
+
Billing dimensions only (what is billed and how it scales). Pricing page: <https://cloud.google.com/bigtable/pricing> (the Google Cloud pricing calculator is linked from it).
|
|
45
|
+
|
|
46
|
+
- Node compute is billed hourly on the maximum nodes in the hour, one-hour minimum per node; the node type depends on the edition [BT-E111].
|
|
47
|
+
- Storage is billed on physical table size (SSD, HDD or infrequent access tiers); every cluster holds its own copy, so replicated instances multiply storage [BT-E110] [BT-E111].
|
|
48
|
+
- Network: bandwidth is billed, including replication writes to clusters in other regions, and restore or copy across regions [BT-E111] [BT-E105].
|
|
49
|
+
- Backups: backup storage is billed (standard incrementally, hot as the full logical copy); create, copy and restore operations themselves are not charged [BT-E105] [BT-E113].
|
|
50
|
+
- Data Boost is billed in serverless processing unit seconds with a per-request minimum and no extra storage or network fee [BT-E112].
|
|
51
|
+
- Tiered storage SSD-to-infrequent-access data movement is billed on the compaction SKU [BT-E113].
|
|
52
|
+
|
|
53
|
+
## Monitoring
|
|
54
|
+
|
|
55
|
+
**Status:** VERIFIED
|
|
56
|
+
|
|
57
|
+
- Bigtable exports metrics to Cloud Monitoring, viewable in the console, Metrics Explorer and the Monitoring API; resource type is Cloud Bigtable Cluster [BT-E114].
|
|
58
|
+
- Key metrics: average CPU utilization, hottest-node CPU, CPU by app profile/method/table, storage utilization, replication latency, system error rate, read and write latency [BT-E115].
|
|
59
|
+
- The documented alert is on `bigtable.googleapis.com/cluster/storage_utilization` at about 70% [BT-E114] [BT-E116].
|
|
60
|
+
- Exceeding the per-node storage hard limit makes writes to all clusters in the instance fail [BT-E116].
|
|
61
|
+
|
|
62
|
+
## Performance
|
|
63
|
+
|
|
64
|
+
**Status:** VERIFIED
|
|
65
|
+
|
|
66
|
+
- Keep CPU below 60% for latency-sensitive workloads and below 90% for throughput-oriented ones; autoscaling is recommended [BT-E117] [BT-E12].
|
|
67
|
+
- Hot tablets (tablets using a disproportionate share of node CPU) cause latency and replication delay; a list of up to 50 per cluster is available [BT-E118].
|
|
68
|
+
- Hotspots from schema design and sequential keys concentrate load and can affect other tables [BT-E119] [BT-E03].
|
|
69
|
+
- Cold starts and low QPS raise latency; keep connections warm [BT-E120].
|
|
70
|
+
- Row, cell and storage limits drive sizing [BT-E10].
|
|
71
|
+
|
|
72
|
+
## IAM
|
|
73
|
+
|
|
74
|
+
**Status:** VERIFIED
|
|
75
|
+
|
|
76
|
+
- IAM applies at project, instance, cluster, table, backup, authorized view and continuous materialized view levels, with downward inheritance; allUsers and allAuthenticatedUsers cannot be granted [BT-E121].
|
|
77
|
+
- Predefined roles: `roles/bigtable.admin`, `roles/bigtable.user`, `roles/bigtable.reader`, `roles/bigtable.viewer` [BT-E13].
|
|
78
|
+
- Least privilege: grant at table, backup or authorized view level (write without read, deny restore or delete, read one view) [BT-E122] [BT-E13].
|
|
79
|
+
|
|
80
|
+
## Tagging
|
|
81
|
+
|
|
82
|
+
**Status:** VERIFIED
|
|
83
|
+
|
|
84
|
+
- Resource tags can be attached to Bigtable instances (needs `roles/bigtable.admin` plus tag permissions) and used in conditional IAM allow or deny policies [BT-E123].
|
|
85
|
+
- Labels remain the mechanism for grouping instances for automation and billing; tags and labels work independently [BT-E123].
|
|
86
|
+
|
|
87
|
+
## Encryption
|
|
88
|
+
|
|
89
|
+
**Status:** PARTIAL
|
|
90
|
+
|
|
91
|
+
- At rest: encrypted by default with Google default encryption; CMEK through Cloud KMS (including Autokey) is optional [BT-E124].
|
|
92
|
+
- CMEK is cluster-level only, key in the cluster's region, immutable once set, no conversion in either direction; inaccessible keys for over 30 days lead to automatic deletion [BT-E125].
|
|
93
|
+
- Disabling a key cascades to disable all clusters; disable all keys together [BT-E126].
|
|
94
|
+
- Some data stays under default encryption (range-boundary row keys, some timestamps, debug data) [BT-E127].
|
|
95
|
+
- In transit: no Bigtable-specific page on transport encryption was retrieved; not asserted here.
|
|
96
|
+
|
|
97
|
+
## Network isolation
|
|
98
|
+
|
|
99
|
+
**Status:** PARTIAL
|
|
100
|
+
|
|
101
|
+
- VPC Service Controls: Bigtable is supported (GA) and perimeters restricting `bigtable.googleapis.com` also restrict the admin service [BT-E128].
|
|
102
|
+
- Private Service Connect backends support the global Bigtable APIs [BT-E129].
|
|
103
|
+
- Private Google Access can reach Google APIs from private-IP hosts and combines with a VPC Service Controls perimeter [BT-E130].
|
|
104
|
+
- Not settled: Bigtable has no documented per-instance toggle to disable public endpoints; none was found.
|
|
105
|
+
|
|
106
|
+
## Audit logging
|
|
107
|
+
|
|
108
|
+
**Status:** VERIFIED
|
|
109
|
+
|
|
110
|
+
- Cloud Audit Logs cover Bigtable under service name `bigtable.googleapis.com`; ADMIN_WRITE methods produce Admin Activity logs [BT-E131].
|
|
111
|
+
- Data-plane operations (DATA_READ, DATA_WRITE, ADMIN_READ methods such as readRows and mutateRows) produce Data Access logs, which must be enabled and have cost implications [BT-E131].
|
|
@@ -4,8 +4,8 @@ description: "Build, configure, and operate Firebase-powered web and mobile appl
|
|
|
4
4
|
allowed-tools: Read Grep Glob Bash(npm install:*) Bash(firebase:*)
|
|
5
5
|
metadata:
|
|
6
6
|
author: "github: VincentChuWaiChow"
|
|
7
|
-
version: "0.1.
|
|
8
|
-
updated: "2026-
|
|
7
|
+
version: "0.1.1"
|
|
8
|
+
updated: "2026-11-08"
|
|
9
9
|
category: platform
|
|
10
10
|
---
|
|
11
11
|
|
|
@@ -37,7 +37,8 @@ Load only when needed:
|
|
|
37
37
|
|
|
38
38
|
| Scenario | Trigger Keywords | Reference |
|
|
39
39
|
|---|---|---|
|
|
40
|
-
| Firestore data modeling | collection, document, subcollection, NoSQL schema, query design | references/firestore.md |
|
|
40
|
+
| Firestore data modeling | collection, document, subcollection, NoSQL schema, query design, index, transaction, TTL, PITR | [references/firestore.md](references/firestore.md) (claims cite [references/evidence-ledger.md](references/evidence-ledger.md)) |
|
|
41
|
+
| Firestore operations | backup, PITR, DR, replication, cost, billing, monitoring, IAM, tags, CMEK, VPC Service Controls, audit logs | Native mode: [references/firestore-operations.md](references/firestore-operations.md); MongoDB compatibility: [references/firestore-mongodb-operations.md](references/firestore-mongodb-operations.md) |
|
|
41
42
|
| Authentication | auth, sign-in, OAuth, email, phone, anonymous, custom claims | references/auth.md |
|
|
42
43
|
| Security Rules | rules, allow, deny, Firestore rules, Storage rules | references/security-rules.md |
|
|
43
44
|
| Cloud Functions | functions, trigger, callable, HTTP, Pub/Sub, Firestore trigger | references/functions.md |
|
|
@@ -46,6 +47,8 @@ Load only when needed:
|
|
|
46
47
|
| Emulator Suite | local testing, emulator, integration test | references/emulators.md |
|
|
47
48
|
| Firebase Extensions | extension, marketplace, prebuilt | references/extensions.md |
|
|
48
49
|
|
|
50
|
+
- [Audit](references/commands/audit.md) — offline or live audit against the operations reference; load only when an audit is requested.
|
|
51
|
+
|
|
49
52
|
## Core Operating Rules
|
|
50
53
|
|
|
51
54
|
- Firebase SDKs come in Web (v9 modular), React Native, Flutter, iOS (Swift), and Android (Kotlin/Java) variants. Always confirm the platform before providing SDK code.
|
|
@@ -3,7 +3,14 @@
|
|
|
3
3
|
"name": "GCP Firebase Developer",
|
|
4
4
|
"type": "skill",
|
|
5
5
|
"provider": "gcp",
|
|
6
|
-
"harnesses": [
|
|
6
|
+
"harnesses": [
|
|
7
|
+
"codex",
|
|
8
|
+
"claude-code",
|
|
9
|
+
"cursor",
|
|
10
|
+
"gemini",
|
|
11
|
+
"kiro",
|
|
12
|
+
"other"
|
|
13
|
+
],
|
|
7
14
|
"summary": "Build, configure, and operate Firebase-powered web and mobile applications — covering Firestore, Firebase Auth, Firebase Hosting, Cloud Functions for Firebase, Firebase Storage, App Check, Remote Config, and Analytics.",
|
|
8
15
|
"source_type": "original",
|
|
9
16
|
"official_docs": [
|
|
@@ -12,11 +19,14 @@
|
|
|
12
19
|
"https://firebase.google.com/docs/auth",
|
|
13
20
|
"https://firebase.google.com/docs/hosting",
|
|
14
21
|
"https://firebase.google.com/docs/functions",
|
|
15
|
-
"https://firebase.google.com/docs/app-check"
|
|
22
|
+
"https://firebase.google.com/docs/app-check",
|
|
23
|
+
"https://firebase.google.com/docs/firestore/quotas",
|
|
24
|
+
"https://firebase.google.com/docs/firestore/transaction-data-contention",
|
|
25
|
+
"https://firebase.google.com/docs/firestore/editions"
|
|
16
26
|
],
|
|
17
27
|
"security_notes": "Read-only skill. Do not deploy to production, modify Firestore security rules, or change Firebase project settings without explicit approval. Client config (apiKey, projectId) is public — service account keys are private and must never be embedded in client code.",
|
|
18
|
-
"last_verified": "2026-
|
|
28
|
+
"last_verified": "2026-11-08",
|
|
19
29
|
"path": "skills/gcp/gcp-firebase-developer",
|
|
20
30
|
"author": "github: VincentChuWaiChow",
|
|
21
|
-
"version": "0.1.
|
|
31
|
+
"version": "0.1.1"
|
|
22
32
|
}
|