Skip to main content

GCP Big Table Admin Table

Google Cloud Bigtable stores data in sparsely populated, massively scalable tables.
A Bigtable Table is the fundamental container for rows, columns, column families and the data itself.
The Admin Table resource exposed by the Cloud Bigtable Admin API represents the metadata for one of these tables inside a particular Bigtable instance (for example its column-family schema, granularity, garbage-collection rules, encryption settings and so on).
For further details see the official documentation: https://cloud.google.com/bigtable/docs/reference/admin/rest/v2/projects.instances.tables

Terrafrom Mappings:

  • google_bigtable_table.id

Supported Methods​

  • GET: Get a gcp-big-table-admin-table by its "instances|tables"
  • LIST
  • SEARCH: Search for BigTable tables in an instance. Use the format "instance_name" or "projects/[project_id]/instances/[instance_name]/tables/[table_name]" which is supported for terraform mappings.

gcp-big-table-admin-table​

Bigtable tables can reference other tables via backup-to-restore operations or through IAM policy bindings that grant access to specific tables.
Where such references are detected Overmind links the current table to the other gcp-big-table-admin-table resources.

gcp-big-table-admin-backup​

A table can have one or more point-in-time Backups stored in the same Bigtable instance.
Each backup therefore links back to the source table, and conversely the table links to any backups that were created from it.

gcp-big-table-admin-instance​

Every Bigtable table lives inside exactly one Bigtable Instance.
The relationship is parent-child: the instance is the parent, the table is the child.
Overmind represents this by linking each gcp-big-table-admin-table to the gcp-big-table-admin-instance that owns it.