gcp.bigtable.Instance
Explore with Pulumi AI
+—
subcategory: “Cloud Bigtable” description: |- Creates a Google Bigtable instance.
gcp.bigtable.Instance
Creates a Google Bigtable instance. For more information see:
- API documentation
- How-to Guides
Example Usage
Simple Instance
using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Gcp = Pulumi.Gcp;
return await Deployment.RunAsync(() =>
{
var production_instance = new Gcp.BigTable.Instance("production-instance", new()
{
Clusters = new[]
{
new Gcp.BigTable.Inputs.InstanceClusterArgs
{
ClusterId = "tf-instance-cluster",
NumNodes = 1,
StorageType = "HDD",
},
},
Labels =
{
{ "my-label", "prod-label" },
},
});
});
package main
import (
"github.com/pulumi/pulumi-gcp/sdk/v6/go/gcp/bigtable"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)
func main() {
pulumi.Run(func(ctx *pulumi.Context) error {
_, err := bigtable.NewInstance(ctx, "production-instance", &bigtable.InstanceArgs{
Clusters: bigtable.InstanceClusterArray{
&bigtable.InstanceClusterArgs{
ClusterId: pulumi.String("tf-instance-cluster"),
NumNodes: pulumi.Int(1),
StorageType: pulumi.String("HDD"),
},
},
Labels: pulumi.StringMap{
"my-label": pulumi.String("prod-label"),
},
})
if err != nil {
return err
}
return nil
})
}
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.gcp.bigtable.Instance;
import com.pulumi.gcp.bigtable.InstanceArgs;
import com.pulumi.gcp.bigtable.inputs.InstanceClusterArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;
public class App {
public static void main(String[] args) {
Pulumi.run(App::stack);
}
public static void stack(Context ctx) {
var production_instance = new Instance("production-instance", InstanceArgs.builder()
.clusters(InstanceClusterArgs.builder()
.clusterId("tf-instance-cluster")
.numNodes(1)
.storageType("HDD")
.build())
.labels(Map.of("my-label", "prod-label"))
.build());
}
}
import pulumi
import pulumi_gcp as gcp
production_instance = gcp.bigtable.Instance("production-instance",
clusters=[gcp.bigtable.InstanceClusterArgs(
cluster_id="tf-instance-cluster",
num_nodes=1,
storage_type="HDD",
)],
labels={
"my-label": "prod-label",
})
import * as pulumi from "@pulumi/pulumi";
import * as gcp from "@pulumi/gcp";
const production_instance = new gcp.bigtable.Instance("production-instance", {
clusters: [{
clusterId: "tf-instance-cluster",
numNodes: 1,
storageType: "HDD",
}],
labels: {
"my-label": "prod-label",
},
});
resources:
production-instance:
type: gcp:bigtable:Instance
properties:
clusters:
- clusterId: tf-instance-cluster
numNodes: 1
storageType: HDD
labels:
my-label: prod-label
Replicated Instance
using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Gcp = Pulumi.Gcp;
return await Deployment.RunAsync(() =>
{
var production_instance = new Gcp.BigTable.Instance("production-instance", new()
{
Clusters = new[]
{
new Gcp.BigTable.Inputs.InstanceClusterArgs
{
ClusterId = "tf-instance-cluster1",
NumNodes = 1,
StorageType = "HDD",
Zone = "us-central1-c",
},
new Gcp.BigTable.Inputs.InstanceClusterArgs
{
AutoscalingConfig = new Gcp.BigTable.Inputs.InstanceClusterAutoscalingConfigArgs
{
CpuTarget = 50,
MaxNodes = 3,
MinNodes = 1,
},
ClusterId = "tf-instance-cluster2",
StorageType = "HDD",
Zone = "us-central1-b",
},
},
Labels =
{
{ "my-label", "prod-label" },
},
});
});
package main
import (
"github.com/pulumi/pulumi-gcp/sdk/v6/go/gcp/bigtable"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)
func main() {
pulumi.Run(func(ctx *pulumi.Context) error {
_, err := bigtable.NewInstance(ctx, "production-instance", &bigtable.InstanceArgs{
Clusters: bigtable.InstanceClusterArray{
&bigtable.InstanceClusterArgs{
ClusterId: pulumi.String("tf-instance-cluster1"),
NumNodes: pulumi.Int(1),
StorageType: pulumi.String("HDD"),
Zone: pulumi.String("us-central1-c"),
},
&bigtable.InstanceClusterArgs{
AutoscalingConfig: &bigtable.InstanceClusterAutoscalingConfigArgs{
CpuTarget: pulumi.Int(50),
MaxNodes: pulumi.Int(3),
MinNodes: pulumi.Int(1),
},
ClusterId: pulumi.String("tf-instance-cluster2"),
StorageType: pulumi.String("HDD"),
Zone: pulumi.String("us-central1-b"),
},
},
Labels: pulumi.StringMap{
"my-label": pulumi.String("prod-label"),
},
})
if err != nil {
return err
}
return nil
})
}
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.gcp.bigtable.Instance;
import com.pulumi.gcp.bigtable.InstanceArgs;
import com.pulumi.gcp.bigtable.inputs.InstanceClusterArgs;
import com.pulumi.gcp.bigtable.inputs.InstanceClusterAutoscalingConfigArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;
public class App {
public static void main(String[] args) {
Pulumi.run(App::stack);
}
public static void stack(Context ctx) {
var production_instance = new Instance("production-instance", InstanceArgs.builder()
.clusters(
InstanceClusterArgs.builder()
.clusterId("tf-instance-cluster1")
.numNodes(1)
.storageType("HDD")
.zone("us-central1-c")
.build(),
InstanceClusterArgs.builder()
.autoscalingConfig(InstanceClusterAutoscalingConfigArgs.builder()
.cpuTarget(50)
.maxNodes(3)
.minNodes(1)
.build())
.clusterId("tf-instance-cluster2")
.storageType("HDD")
.zone("us-central1-b")
.build())
.labels(Map.of("my-label", "prod-label"))
.build());
}
}
import pulumi
import pulumi_gcp as gcp
production_instance = gcp.bigtable.Instance("production-instance",
clusters=[
gcp.bigtable.InstanceClusterArgs(
cluster_id="tf-instance-cluster1",
num_nodes=1,
storage_type="HDD",
zone="us-central1-c",
),
gcp.bigtable.InstanceClusterArgs(
autoscaling_config=gcp.bigtable.InstanceClusterAutoscalingConfigArgs(
cpu_target=50,
max_nodes=3,
min_nodes=1,
),
cluster_id="tf-instance-cluster2",
storage_type="HDD",
zone="us-central1-b",
),
],
labels={
"my-label": "prod-label",
})
import * as pulumi from "@pulumi/pulumi";
import * as gcp from "@pulumi/gcp";
const production_instance = new gcp.bigtable.Instance("production-instance", {
clusters: [
{
clusterId: "tf-instance-cluster1",
numNodes: 1,
storageType: "HDD",
zone: "us-central1-c",
},
{
autoscalingConfig: {
cpuTarget: 50,
maxNodes: 3,
minNodes: 1,
},
clusterId: "tf-instance-cluster2",
storageType: "HDD",
zone: "us-central1-b",
},
],
labels: {
"my-label": "prod-label",
},
});
resources:
production-instance:
type: gcp:bigtable:Instance
properties:
clusters:
- clusterId: tf-instance-cluster1
numNodes: 1
storageType: HDD
zone: us-central1-c
- autoscalingConfig:
cpuTarget: 50
maxNodes: 3
minNodes: 1
clusterId: tf-instance-cluster2
storageType: HDD
zone: us-central1-b
labels:
my-label: prod-label
Create Instance Resource
new Instance(name: string, args?: InstanceArgs, opts?: CustomResourceOptions);
@overload
def Instance(resource_name: str,
opts: Optional[ResourceOptions] = None,
clusters: Optional[Sequence[InstanceClusterArgs]] = None,
deletion_protection: Optional[bool] = None,
display_name: Optional[str] = None,
instance_type: Optional[str] = None,
labels: Optional[Mapping[str, str]] = None,
name: Optional[str] = None,
project: Optional[str] = None)
@overload
def Instance(resource_name: str,
args: Optional[InstanceArgs] = None,
opts: Optional[ResourceOptions] = None)
func NewInstance(ctx *Context, name string, args *InstanceArgs, opts ...ResourceOption) (*Instance, error)
public Instance(string name, InstanceArgs? args = null, CustomResourceOptions? opts = null)
public Instance(String name, InstanceArgs args)
public Instance(String name, InstanceArgs args, CustomResourceOptions options)
type: gcp:bigtable:Instance
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args InstanceArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- resource_name str
- The unique name of the resource.
- args InstanceArgs
- The arguments to resource properties.
- opts ResourceOptions
- Bag of options to control resource's behavior.
- ctx Context
- Context object for the current deployment.
- name string
- The unique name of the resource.
- args InstanceArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args InstanceArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- name String
- The unique name of the resource.
- args InstanceArgs
- The arguments to resource properties.
- options CustomResourceOptions
- Bag of options to control resource's behavior.
Instance Resource Properties
To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.
Inputs
The Instance resource accepts the following input properties:
- Clusters
List<Instance
Cluster Args> A block of cluster configuration options. This can be specified at least once, and up to as many as possible within 8 cloud regions. Removing the field entirely from the config will cause the provider to default to the backend value. See structure below.
- Deletion
Protection bool Whether or not to allow this provider to destroy the instance. Unless this field is set to false in the statefile, a
pulumi destroy
orpulumi up
that would delete the instance will fail.- Display
Name string The human-readable display name of the Bigtable instance. Defaults to the instance
name
.- Instance
Type string The instance type to create. One of
"DEVELOPMENT"
or"PRODUCTION"
. Defaults to"PRODUCTION"
. It is recommended to leave this field unspecified since the distinction between"DEVELOPMENT"
and"PRODUCTION"
instances is going away, and all instances will become"PRODUCTION"
instances. This means that new and existing"DEVELOPMENT"
instances will be converted to"PRODUCTION"
instances. It is recommended for users to use"PRODUCTION"
instances in any case, since a 1-node"PRODUCTION"
instance is functionally identical to a"DEVELOPMENT"
instance, but without the accompanying restrictions.It is recommended to leave this field unspecified since the distinction between "DEVELOPMENT" and "PRODUCTION" instances is going away, and all instances will become "PRODUCTION" instances. This means that new and existing "DEVELOPMENT" instances will be converted to "PRODUCTION" instances. It is recommended for users to use "PRODUCTION" instances in any case, since a 1-node "PRODUCTION" instance is functionally identical to a "DEVELOPMENT" instance, but without the accompanying restrictions.
- Labels Dictionary<string, string>
A set of key/value label pairs to assign to the resource. Label keys must follow the requirements at https://cloud.google.com/resource-manager/docs/creating-managing-labels#requirements.
- Name string
The name (also called Instance Id in the Cloud Console) of the Cloud Bigtable instance. Must be 6-33 characters and must only contain hyphens, lowercase letters and numbers.
- Project string
The ID of the project in which the resource belongs. If it is not provided, the provider project is used.
- Clusters
[]Instance
Cluster Args A block of cluster configuration options. This can be specified at least once, and up to as many as possible within 8 cloud regions. Removing the field entirely from the config will cause the provider to default to the backend value. See structure below.
- Deletion
Protection bool Whether or not to allow this provider to destroy the instance. Unless this field is set to false in the statefile, a
pulumi destroy
orpulumi up
that would delete the instance will fail.- Display
Name string The human-readable display name of the Bigtable instance. Defaults to the instance
name
.- Instance
Type string The instance type to create. One of
"DEVELOPMENT"
or"PRODUCTION"
. Defaults to"PRODUCTION"
. It is recommended to leave this field unspecified since the distinction between"DEVELOPMENT"
and"PRODUCTION"
instances is going away, and all instances will become"PRODUCTION"
instances. This means that new and existing"DEVELOPMENT"
instances will be converted to"PRODUCTION"
instances. It is recommended for users to use"PRODUCTION"
instances in any case, since a 1-node"PRODUCTION"
instance is functionally identical to a"DEVELOPMENT"
instance, but without the accompanying restrictions.It is recommended to leave this field unspecified since the distinction between "DEVELOPMENT" and "PRODUCTION" instances is going away, and all instances will become "PRODUCTION" instances. This means that new and existing "DEVELOPMENT" instances will be converted to "PRODUCTION" instances. It is recommended for users to use "PRODUCTION" instances in any case, since a 1-node "PRODUCTION" instance is functionally identical to a "DEVELOPMENT" instance, but without the accompanying restrictions.
- Labels map[string]string
A set of key/value label pairs to assign to the resource. Label keys must follow the requirements at https://cloud.google.com/resource-manager/docs/creating-managing-labels#requirements.
- Name string
The name (also called Instance Id in the Cloud Console) of the Cloud Bigtable instance. Must be 6-33 characters and must only contain hyphens, lowercase letters and numbers.
- Project string
The ID of the project in which the resource belongs. If it is not provided, the provider project is used.
- clusters
List<Instance
Cluster Args> A block of cluster configuration options. This can be specified at least once, and up to as many as possible within 8 cloud regions. Removing the field entirely from the config will cause the provider to default to the backend value. See structure below.
- deletion
Protection Boolean Whether or not to allow this provider to destroy the instance. Unless this field is set to false in the statefile, a
pulumi destroy
orpulumi up
that would delete the instance will fail.- display
Name String The human-readable display name of the Bigtable instance. Defaults to the instance
name
.- instance
Type String The instance type to create. One of
"DEVELOPMENT"
or"PRODUCTION"
. Defaults to"PRODUCTION"
. It is recommended to leave this field unspecified since the distinction between"DEVELOPMENT"
and"PRODUCTION"
instances is going away, and all instances will become"PRODUCTION"
instances. This means that new and existing"DEVELOPMENT"
instances will be converted to"PRODUCTION"
instances. It is recommended for users to use"PRODUCTION"
instances in any case, since a 1-node"PRODUCTION"
instance is functionally identical to a"DEVELOPMENT"
instance, but without the accompanying restrictions.It is recommended to leave this field unspecified since the distinction between "DEVELOPMENT" and "PRODUCTION" instances is going away, and all instances will become "PRODUCTION" instances. This means that new and existing "DEVELOPMENT" instances will be converted to "PRODUCTION" instances. It is recommended for users to use "PRODUCTION" instances in any case, since a 1-node "PRODUCTION" instance is functionally identical to a "DEVELOPMENT" instance, but without the accompanying restrictions.
- labels Map<String,String>
A set of key/value label pairs to assign to the resource. Label keys must follow the requirements at https://cloud.google.com/resource-manager/docs/creating-managing-labels#requirements.
- name String
The name (also called Instance Id in the Cloud Console) of the Cloud Bigtable instance. Must be 6-33 characters and must only contain hyphens, lowercase letters and numbers.
- project String
The ID of the project in which the resource belongs. If it is not provided, the provider project is used.
- clusters
Instance
Cluster Args[] A block of cluster configuration options. This can be specified at least once, and up to as many as possible within 8 cloud regions. Removing the field entirely from the config will cause the provider to default to the backend value. See structure below.
- deletion
Protection boolean Whether or not to allow this provider to destroy the instance. Unless this field is set to false in the statefile, a
pulumi destroy
orpulumi up
that would delete the instance will fail.- display
Name string The human-readable display name of the Bigtable instance. Defaults to the instance
name
.- instance
Type string The instance type to create. One of
"DEVELOPMENT"
or"PRODUCTION"
. Defaults to"PRODUCTION"
. It is recommended to leave this field unspecified since the distinction between"DEVELOPMENT"
and"PRODUCTION"
instances is going away, and all instances will become"PRODUCTION"
instances. This means that new and existing"DEVELOPMENT"
instances will be converted to"PRODUCTION"
instances. It is recommended for users to use"PRODUCTION"
instances in any case, since a 1-node"PRODUCTION"
instance is functionally identical to a"DEVELOPMENT"
instance, but without the accompanying restrictions.It is recommended to leave this field unspecified since the distinction between "DEVELOPMENT" and "PRODUCTION" instances is going away, and all instances will become "PRODUCTION" instances. This means that new and existing "DEVELOPMENT" instances will be converted to "PRODUCTION" instances. It is recommended for users to use "PRODUCTION" instances in any case, since a 1-node "PRODUCTION" instance is functionally identical to a "DEVELOPMENT" instance, but without the accompanying restrictions.
- labels {[key: string]: string}
A set of key/value label pairs to assign to the resource. Label keys must follow the requirements at https://cloud.google.com/resource-manager/docs/creating-managing-labels#requirements.
- name string
The name (also called Instance Id in the Cloud Console) of the Cloud Bigtable instance. Must be 6-33 characters and must only contain hyphens, lowercase letters and numbers.
- project string
The ID of the project in which the resource belongs. If it is not provided, the provider project is used.
- clusters
Sequence[Instance
Cluster Args] A block of cluster configuration options. This can be specified at least once, and up to as many as possible within 8 cloud regions. Removing the field entirely from the config will cause the provider to default to the backend value. See structure below.
- deletion_
protection bool Whether or not to allow this provider to destroy the instance. Unless this field is set to false in the statefile, a
pulumi destroy
orpulumi up
that would delete the instance will fail.- display_
name str The human-readable display name of the Bigtable instance. Defaults to the instance
name
.- instance_
type str The instance type to create. One of
"DEVELOPMENT"
or"PRODUCTION"
. Defaults to"PRODUCTION"
. It is recommended to leave this field unspecified since the distinction between"DEVELOPMENT"
and"PRODUCTION"
instances is going away, and all instances will become"PRODUCTION"
instances. This means that new and existing"DEVELOPMENT"
instances will be converted to"PRODUCTION"
instances. It is recommended for users to use"PRODUCTION"
instances in any case, since a 1-node"PRODUCTION"
instance is functionally identical to a"DEVELOPMENT"
instance, but without the accompanying restrictions.It is recommended to leave this field unspecified since the distinction between "DEVELOPMENT" and "PRODUCTION" instances is going away, and all instances will become "PRODUCTION" instances. This means that new and existing "DEVELOPMENT" instances will be converted to "PRODUCTION" instances. It is recommended for users to use "PRODUCTION" instances in any case, since a 1-node "PRODUCTION" instance is functionally identical to a "DEVELOPMENT" instance, but without the accompanying restrictions.
- labels Mapping[str, str]
A set of key/value label pairs to assign to the resource. Label keys must follow the requirements at https://cloud.google.com/resource-manager/docs/creating-managing-labels#requirements.
- name str
The name (also called Instance Id in the Cloud Console) of the Cloud Bigtable instance. Must be 6-33 characters and must only contain hyphens, lowercase letters and numbers.
- project str
The ID of the project in which the resource belongs. If it is not provided, the provider project is used.
- clusters List<Property Map>
A block of cluster configuration options. This can be specified at least once, and up to as many as possible within 8 cloud regions. Removing the field entirely from the config will cause the provider to default to the backend value. See structure below.
- deletion
Protection Boolean Whether or not to allow this provider to destroy the instance. Unless this field is set to false in the statefile, a
pulumi destroy
orpulumi up
that would delete the instance will fail.- display
Name String The human-readable display name of the Bigtable instance. Defaults to the instance
name
.- instance
Type String The instance type to create. One of
"DEVELOPMENT"
or"PRODUCTION"
. Defaults to"PRODUCTION"
. It is recommended to leave this field unspecified since the distinction between"DEVELOPMENT"
and"PRODUCTION"
instances is going away, and all instances will become"PRODUCTION"
instances. This means that new and existing"DEVELOPMENT"
instances will be converted to"PRODUCTION"
instances. It is recommended for users to use"PRODUCTION"
instances in any case, since a 1-node"PRODUCTION"
instance is functionally identical to a"DEVELOPMENT"
instance, but without the accompanying restrictions.It is recommended to leave this field unspecified since the distinction between "DEVELOPMENT" and "PRODUCTION" instances is going away, and all instances will become "PRODUCTION" instances. This means that new and existing "DEVELOPMENT" instances will be converted to "PRODUCTION" instances. It is recommended for users to use "PRODUCTION" instances in any case, since a 1-node "PRODUCTION" instance is functionally identical to a "DEVELOPMENT" instance, but without the accompanying restrictions.
- labels Map<String>
A set of key/value label pairs to assign to the resource. Label keys must follow the requirements at https://cloud.google.com/resource-manager/docs/creating-managing-labels#requirements.
- name String
The name (also called Instance Id in the Cloud Console) of the Cloud Bigtable instance. Must be 6-33 characters and must only contain hyphens, lowercase letters and numbers.
- project String
The ID of the project in which the resource belongs. If it is not provided, the provider project is used.
Outputs
All input properties are implicitly available as output properties. Additionally, the Instance resource produces the following output properties:
- Id string
The provider-assigned unique ID for this managed resource.
- Id string
The provider-assigned unique ID for this managed resource.
- id String
The provider-assigned unique ID for this managed resource.
- id string
The provider-assigned unique ID for this managed resource.
- id str
The provider-assigned unique ID for this managed resource.
- id String
The provider-assigned unique ID for this managed resource.
Look up Existing Instance Resource
Get an existing Instance resource’s state with the given name, ID, and optional extra properties used to qualify the lookup.
public static get(name: string, id: Input<ID>, state?: InstanceState, opts?: CustomResourceOptions): Instance
@staticmethod
def get(resource_name: str,
id: str,
opts: Optional[ResourceOptions] = None,
clusters: Optional[Sequence[InstanceClusterArgs]] = None,
deletion_protection: Optional[bool] = None,
display_name: Optional[str] = None,
instance_type: Optional[str] = None,
labels: Optional[Mapping[str, str]] = None,
name: Optional[str] = None,
project: Optional[str] = None) -> Instance
func GetInstance(ctx *Context, name string, id IDInput, state *InstanceState, opts ...ResourceOption) (*Instance, error)
public static Instance Get(string name, Input<string> id, InstanceState? state, CustomResourceOptions? opts = null)
public static Instance get(String name, Output<String> id, InstanceState state, CustomResourceOptions options)
Resource lookup is not supported in YAML
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- resource_name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- Clusters
List<Instance
Cluster Args> A block of cluster configuration options. This can be specified at least once, and up to as many as possible within 8 cloud regions. Removing the field entirely from the config will cause the provider to default to the backend value. See structure below.
- Deletion
Protection bool Whether or not to allow this provider to destroy the instance. Unless this field is set to false in the statefile, a
pulumi destroy
orpulumi up
that would delete the instance will fail.- Display
Name string The human-readable display name of the Bigtable instance. Defaults to the instance
name
.- Instance
Type string The instance type to create. One of
"DEVELOPMENT"
or"PRODUCTION"
. Defaults to"PRODUCTION"
. It is recommended to leave this field unspecified since the distinction between"DEVELOPMENT"
and"PRODUCTION"
instances is going away, and all instances will become"PRODUCTION"
instances. This means that new and existing"DEVELOPMENT"
instances will be converted to"PRODUCTION"
instances. It is recommended for users to use"PRODUCTION"
instances in any case, since a 1-node"PRODUCTION"
instance is functionally identical to a"DEVELOPMENT"
instance, but without the accompanying restrictions.It is recommended to leave this field unspecified since the distinction between "DEVELOPMENT" and "PRODUCTION" instances is going away, and all instances will become "PRODUCTION" instances. This means that new and existing "DEVELOPMENT" instances will be converted to "PRODUCTION" instances. It is recommended for users to use "PRODUCTION" instances in any case, since a 1-node "PRODUCTION" instance is functionally identical to a "DEVELOPMENT" instance, but without the accompanying restrictions.
- Labels Dictionary<string, string>
A set of key/value label pairs to assign to the resource. Label keys must follow the requirements at https://cloud.google.com/resource-manager/docs/creating-managing-labels#requirements.
- Name string
The name (also called Instance Id in the Cloud Console) of the Cloud Bigtable instance. Must be 6-33 characters and must only contain hyphens, lowercase letters and numbers.
- Project string
The ID of the project in which the resource belongs. If it is not provided, the provider project is used.
- Clusters
[]Instance
Cluster Args A block of cluster configuration options. This can be specified at least once, and up to as many as possible within 8 cloud regions. Removing the field entirely from the config will cause the provider to default to the backend value. See structure below.
- Deletion
Protection bool Whether or not to allow this provider to destroy the instance. Unless this field is set to false in the statefile, a
pulumi destroy
orpulumi up
that would delete the instance will fail.- Display
Name string The human-readable display name of the Bigtable instance. Defaults to the instance
name
.- Instance
Type string The instance type to create. One of
"DEVELOPMENT"
or"PRODUCTION"
. Defaults to"PRODUCTION"
. It is recommended to leave this field unspecified since the distinction between"DEVELOPMENT"
and"PRODUCTION"
instances is going away, and all instances will become"PRODUCTION"
instances. This means that new and existing"DEVELOPMENT"
instances will be converted to"PRODUCTION"
instances. It is recommended for users to use"PRODUCTION"
instances in any case, since a 1-node"PRODUCTION"
instance is functionally identical to a"DEVELOPMENT"
instance, but without the accompanying restrictions.It is recommended to leave this field unspecified since the distinction between "DEVELOPMENT" and "PRODUCTION" instances is going away, and all instances will become "PRODUCTION" instances. This means that new and existing "DEVELOPMENT" instances will be converted to "PRODUCTION" instances. It is recommended for users to use "PRODUCTION" instances in any case, since a 1-node "PRODUCTION" instance is functionally identical to a "DEVELOPMENT" instance, but without the accompanying restrictions.
- Labels map[string]string
A set of key/value label pairs to assign to the resource. Label keys must follow the requirements at https://cloud.google.com/resource-manager/docs/creating-managing-labels#requirements.
- Name string
The name (also called Instance Id in the Cloud Console) of the Cloud Bigtable instance. Must be 6-33 characters and must only contain hyphens, lowercase letters and numbers.
- Project string
The ID of the project in which the resource belongs. If it is not provided, the provider project is used.
- clusters
List<Instance
Cluster Args> A block of cluster configuration options. This can be specified at least once, and up to as many as possible within 8 cloud regions. Removing the field entirely from the config will cause the provider to default to the backend value. See structure below.
- deletion
Protection Boolean Whether or not to allow this provider to destroy the instance. Unless this field is set to false in the statefile, a
pulumi destroy
orpulumi up
that would delete the instance will fail.- display
Name String The human-readable display name of the Bigtable instance. Defaults to the instance
name
.- instance
Type String The instance type to create. One of
"DEVELOPMENT"
or"PRODUCTION"
. Defaults to"PRODUCTION"
. It is recommended to leave this field unspecified since the distinction between"DEVELOPMENT"
and"PRODUCTION"
instances is going away, and all instances will become"PRODUCTION"
instances. This means that new and existing"DEVELOPMENT"
instances will be converted to"PRODUCTION"
instances. It is recommended for users to use"PRODUCTION"
instances in any case, since a 1-node"PRODUCTION"
instance is functionally identical to a"DEVELOPMENT"
instance, but without the accompanying restrictions.It is recommended to leave this field unspecified since the distinction between "DEVELOPMENT" and "PRODUCTION" instances is going away, and all instances will become "PRODUCTION" instances. This means that new and existing "DEVELOPMENT" instances will be converted to "PRODUCTION" instances. It is recommended for users to use "PRODUCTION" instances in any case, since a 1-node "PRODUCTION" instance is functionally identical to a "DEVELOPMENT" instance, but without the accompanying restrictions.
- labels Map<String,String>
A set of key/value label pairs to assign to the resource. Label keys must follow the requirements at https://cloud.google.com/resource-manager/docs/creating-managing-labels#requirements.
- name String
The name (also called Instance Id in the Cloud Console) of the Cloud Bigtable instance. Must be 6-33 characters and must only contain hyphens, lowercase letters and numbers.
- project String
The ID of the project in which the resource belongs. If it is not provided, the provider project is used.
- clusters
Instance
Cluster Args[] A block of cluster configuration options. This can be specified at least once, and up to as many as possible within 8 cloud regions. Removing the field entirely from the config will cause the provider to default to the backend value. See structure below.
- deletion
Protection boolean Whether or not to allow this provider to destroy the instance. Unless this field is set to false in the statefile, a
pulumi destroy
orpulumi up
that would delete the instance will fail.- display
Name string The human-readable display name of the Bigtable instance. Defaults to the instance
name
.- instance
Type string The instance type to create. One of
"DEVELOPMENT"
or"PRODUCTION"
. Defaults to"PRODUCTION"
. It is recommended to leave this field unspecified since the distinction between"DEVELOPMENT"
and"PRODUCTION"
instances is going away, and all instances will become"PRODUCTION"
instances. This means that new and existing"DEVELOPMENT"
instances will be converted to"PRODUCTION"
instances. It is recommended for users to use"PRODUCTION"
instances in any case, since a 1-node"PRODUCTION"
instance is functionally identical to a"DEVELOPMENT"
instance, but without the accompanying restrictions.It is recommended to leave this field unspecified since the distinction between "DEVELOPMENT" and "PRODUCTION" instances is going away, and all instances will become "PRODUCTION" instances. This means that new and existing "DEVELOPMENT" instances will be converted to "PRODUCTION" instances. It is recommended for users to use "PRODUCTION" instances in any case, since a 1-node "PRODUCTION" instance is functionally identical to a "DEVELOPMENT" instance, but without the accompanying restrictions.
- labels {[key: string]: string}
A set of key/value label pairs to assign to the resource. Label keys must follow the requirements at https://cloud.google.com/resource-manager/docs/creating-managing-labels#requirements.
- name string
The name (also called Instance Id in the Cloud Console) of the Cloud Bigtable instance. Must be 6-33 characters and must only contain hyphens, lowercase letters and numbers.
- project string
The ID of the project in which the resource belongs. If it is not provided, the provider project is used.
- clusters
Sequence[Instance
Cluster Args] A block of cluster configuration options. This can be specified at least once, and up to as many as possible within 8 cloud regions. Removing the field entirely from the config will cause the provider to default to the backend value. See structure below.
- deletion_
protection bool Whether or not to allow this provider to destroy the instance. Unless this field is set to false in the statefile, a
pulumi destroy
orpulumi up
that would delete the instance will fail.- display_
name str The human-readable display name of the Bigtable instance. Defaults to the instance
name
.- instance_
type str The instance type to create. One of
"DEVELOPMENT"
or"PRODUCTION"
. Defaults to"PRODUCTION"
. It is recommended to leave this field unspecified since the distinction between"DEVELOPMENT"
and"PRODUCTION"
instances is going away, and all instances will become"PRODUCTION"
instances. This means that new and existing"DEVELOPMENT"
instances will be converted to"PRODUCTION"
instances. It is recommended for users to use"PRODUCTION"
instances in any case, since a 1-node"PRODUCTION"
instance is functionally identical to a"DEVELOPMENT"
instance, but without the accompanying restrictions.It is recommended to leave this field unspecified since the distinction between "DEVELOPMENT" and "PRODUCTION" instances is going away, and all instances will become "PRODUCTION" instances. This means that new and existing "DEVELOPMENT" instances will be converted to "PRODUCTION" instances. It is recommended for users to use "PRODUCTION" instances in any case, since a 1-node "PRODUCTION" instance is functionally identical to a "DEVELOPMENT" instance, but without the accompanying restrictions.
- labels Mapping[str, str]
A set of key/value label pairs to assign to the resource. Label keys must follow the requirements at https://cloud.google.com/resource-manager/docs/creating-managing-labels#requirements.
- name str
The name (also called Instance Id in the Cloud Console) of the Cloud Bigtable instance. Must be 6-33 characters and must only contain hyphens, lowercase letters and numbers.
- project str
The ID of the project in which the resource belongs. If it is not provided, the provider project is used.
- clusters List<Property Map>
A block of cluster configuration options. This can be specified at least once, and up to as many as possible within 8 cloud regions. Removing the field entirely from the config will cause the provider to default to the backend value. See structure below.
- deletion
Protection Boolean Whether or not to allow this provider to destroy the instance. Unless this field is set to false in the statefile, a
pulumi destroy
orpulumi up
that would delete the instance will fail.- display
Name String The human-readable display name of the Bigtable instance. Defaults to the instance
name
.- instance
Type String The instance type to create. One of
"DEVELOPMENT"
or"PRODUCTION"
. Defaults to"PRODUCTION"
. It is recommended to leave this field unspecified since the distinction between"DEVELOPMENT"
and"PRODUCTION"
instances is going away, and all instances will become"PRODUCTION"
instances. This means that new and existing"DEVELOPMENT"
instances will be converted to"PRODUCTION"
instances. It is recommended for users to use"PRODUCTION"
instances in any case, since a 1-node"PRODUCTION"
instance is functionally identical to a"DEVELOPMENT"
instance, but without the accompanying restrictions.It is recommended to leave this field unspecified since the distinction between "DEVELOPMENT" and "PRODUCTION" instances is going away, and all instances will become "PRODUCTION" instances. This means that new and existing "DEVELOPMENT" instances will be converted to "PRODUCTION" instances. It is recommended for users to use "PRODUCTION" instances in any case, since a 1-node "PRODUCTION" instance is functionally identical to a "DEVELOPMENT" instance, but without the accompanying restrictions.
- labels Map<String>
A set of key/value label pairs to assign to the resource. Label keys must follow the requirements at https://cloud.google.com/resource-manager/docs/creating-managing-labels#requirements.
- name String
The name (also called Instance Id in the Cloud Console) of the Cloud Bigtable instance. Must be 6-33 characters and must only contain hyphens, lowercase letters and numbers.
- project String
The ID of the project in which the resource belongs. If it is not provided, the provider project is used.
Supporting Types
InstanceCluster
- Cluster
Id string The ID of the Cloud Bigtable cluster. Must be 6-30 characters and must only contain hyphens, lowercase letters and numbers.
- Autoscaling
Config InstanceCluster Autoscaling Config Autoscaling config for the cluster, contains the following arguments:
- Kms
Key stringName Describes the Cloud KMS encryption key that will be used to protect the destination Bigtable cluster. The requirements for this key are: 1) The Cloud Bigtable service account associated with the project that contains this cluster must be granted the
cloudkms.cryptoKeyEncrypterDecrypter
role on the CMEK key. 2) Only regional keys can be used and the region of the CMEK key must match the region of the cluster.Note: Removing the field entirely from the config will cause the provider to default to the backend value.
!> Warning: Modifying this field will cause the provider to delete/recreate the entire resource.
!> Warning: Modifying the
storage_type
,zone
orkms_key_name
of an existing cluster (bycluster_id
) will cause the provider to delete/recreate the entiregcp.bigtable.Instance
resource. If these values are changing, use a newcluster_id
.- Num
Nodes int The number of nodes in your Cloud Bigtable cluster. Required, with a minimum of
1
for each cluster in an instance.- Storage
Type string The storage type to use. One of
"SSD"
or"HDD"
. Defaults to"SSD"
.- Zone string
The zone to create the Cloud Bigtable cluster in. If it not specified, the provider zone is used. Each cluster must have a different zone in the same region. Zones that support Bigtable instances are noted on the Cloud Bigtable locations page.
- Cluster
Id string The ID of the Cloud Bigtable cluster. Must be 6-30 characters and must only contain hyphens, lowercase letters and numbers.
- Autoscaling
Config InstanceCluster Autoscaling Config Autoscaling config for the cluster, contains the following arguments:
- Kms
Key stringName Describes the Cloud KMS encryption key that will be used to protect the destination Bigtable cluster. The requirements for this key are: 1) The Cloud Bigtable service account associated with the project that contains this cluster must be granted the
cloudkms.cryptoKeyEncrypterDecrypter
role on the CMEK key. 2) Only regional keys can be used and the region of the CMEK key must match the region of the cluster.Note: Removing the field entirely from the config will cause the provider to default to the backend value.
!> Warning: Modifying this field will cause the provider to delete/recreate the entire resource.
!> Warning: Modifying the
storage_type
,zone
orkms_key_name
of an existing cluster (bycluster_id
) will cause the provider to delete/recreate the entiregcp.bigtable.Instance
resource. If these values are changing, use a newcluster_id
.- Num
Nodes int The number of nodes in your Cloud Bigtable cluster. Required, with a minimum of
1
for each cluster in an instance.- Storage
Type string The storage type to use. One of
"SSD"
or"HDD"
. Defaults to"SSD"
.- Zone string
The zone to create the Cloud Bigtable cluster in. If it not specified, the provider zone is used. Each cluster must have a different zone in the same region. Zones that support Bigtable instances are noted on the Cloud Bigtable locations page.
- cluster
Id String The ID of the Cloud Bigtable cluster. Must be 6-30 characters and must only contain hyphens, lowercase letters and numbers.
- autoscaling
Config InstanceCluster Autoscaling Config Autoscaling config for the cluster, contains the following arguments:
- kms
Key StringName Describes the Cloud KMS encryption key that will be used to protect the destination Bigtable cluster. The requirements for this key are: 1) The Cloud Bigtable service account associated with the project that contains this cluster must be granted the
cloudkms.cryptoKeyEncrypterDecrypter
role on the CMEK key. 2) Only regional keys can be used and the region of the CMEK key must match the region of the cluster.Note: Removing the field entirely from the config will cause the provider to default to the backend value.
!> Warning: Modifying this field will cause the provider to delete/recreate the entire resource.
!> Warning: Modifying the
storage_type
,zone
orkms_key_name
of an existing cluster (bycluster_id
) will cause the provider to delete/recreate the entiregcp.bigtable.Instance
resource. If these values are changing, use a newcluster_id
.- num
Nodes Integer The number of nodes in your Cloud Bigtable cluster. Required, with a minimum of
1
for each cluster in an instance.- storage
Type String The storage type to use. One of
"SSD"
or"HDD"
. Defaults to"SSD"
.- zone String
The zone to create the Cloud Bigtable cluster in. If it not specified, the provider zone is used. Each cluster must have a different zone in the same region. Zones that support Bigtable instances are noted on the Cloud Bigtable locations page.
- cluster
Id string The ID of the Cloud Bigtable cluster. Must be 6-30 characters and must only contain hyphens, lowercase letters and numbers.
- autoscaling
Config InstanceCluster Autoscaling Config Autoscaling config for the cluster, contains the following arguments:
- kms
Key stringName Describes the Cloud KMS encryption key that will be used to protect the destination Bigtable cluster. The requirements for this key are: 1) The Cloud Bigtable service account associated with the project that contains this cluster must be granted the
cloudkms.cryptoKeyEncrypterDecrypter
role on the CMEK key. 2) Only regional keys can be used and the region of the CMEK key must match the region of the cluster.Note: Removing the field entirely from the config will cause the provider to default to the backend value.
!> Warning: Modifying this field will cause the provider to delete/recreate the entire resource.
!> Warning: Modifying the
storage_type
,zone
orkms_key_name
of an existing cluster (bycluster_id
) will cause the provider to delete/recreate the entiregcp.bigtable.Instance
resource. If these values are changing, use a newcluster_id
.- num
Nodes number The number of nodes in your Cloud Bigtable cluster. Required, with a minimum of
1
for each cluster in an instance.- storage
Type string The storage type to use. One of
"SSD"
or"HDD"
. Defaults to"SSD"
.- zone string
The zone to create the Cloud Bigtable cluster in. If it not specified, the provider zone is used. Each cluster must have a different zone in the same region. Zones that support Bigtable instances are noted on the Cloud Bigtable locations page.
- cluster_
id str The ID of the Cloud Bigtable cluster. Must be 6-30 characters and must only contain hyphens, lowercase letters and numbers.
- autoscaling_
config InstanceCluster Autoscaling Config Autoscaling config for the cluster, contains the following arguments:
- kms_
key_ strname Describes the Cloud KMS encryption key that will be used to protect the destination Bigtable cluster. The requirements for this key are: 1) The Cloud Bigtable service account associated with the project that contains this cluster must be granted the
cloudkms.cryptoKeyEncrypterDecrypter
role on the CMEK key. 2) Only regional keys can be used and the region of the CMEK key must match the region of the cluster.Note: Removing the field entirely from the config will cause the provider to default to the backend value.
!> Warning: Modifying this field will cause the provider to delete/recreate the entire resource.
!> Warning: Modifying the
storage_type
,zone
orkms_key_name
of an existing cluster (bycluster_id
) will cause the provider to delete/recreate the entiregcp.bigtable.Instance
resource. If these values are changing, use a newcluster_id
.- num_
nodes int The number of nodes in your Cloud Bigtable cluster. Required, with a minimum of
1
for each cluster in an instance.- storage_
type str The storage type to use. One of
"SSD"
or"HDD"
. Defaults to"SSD"
.- zone str
The zone to create the Cloud Bigtable cluster in. If it not specified, the provider zone is used. Each cluster must have a different zone in the same region. Zones that support Bigtable instances are noted on the Cloud Bigtable locations page.
- cluster
Id String The ID of the Cloud Bigtable cluster. Must be 6-30 characters and must only contain hyphens, lowercase letters and numbers.
- autoscaling
Config Property Map Autoscaling config for the cluster, contains the following arguments:
- kms
Key StringName Describes the Cloud KMS encryption key that will be used to protect the destination Bigtable cluster. The requirements for this key are: 1) The Cloud Bigtable service account associated with the project that contains this cluster must be granted the
cloudkms.cryptoKeyEncrypterDecrypter
role on the CMEK key. 2) Only regional keys can be used and the region of the CMEK key must match the region of the cluster.Note: Removing the field entirely from the config will cause the provider to default to the backend value.
!> Warning: Modifying this field will cause the provider to delete/recreate the entire resource.
!> Warning: Modifying the
storage_type
,zone
orkms_key_name
of an existing cluster (bycluster_id
) will cause the provider to delete/recreate the entiregcp.bigtable.Instance
resource. If these values are changing, use a newcluster_id
.- num
Nodes Number The number of nodes in your Cloud Bigtable cluster. Required, with a minimum of
1
for each cluster in an instance.- storage
Type String The storage type to use. One of
"SSD"
or"HDD"
. Defaults to"SSD"
.- zone String
The zone to create the Cloud Bigtable cluster in. If it not specified, the provider zone is used. Each cluster must have a different zone in the same region. Zones that support Bigtable instances are noted on the Cloud Bigtable locations page.
InstanceClusterAutoscalingConfig
- Cpu
Target int The target CPU utilization for autoscaling, in percentage. Must be between 10 and 80.
- Max
Nodes int The maximum number of nodes for autoscaling.
- Min
Nodes int The minimum number of nodes for autoscaling.
- Storage
Target int The target storage utilization for autoscaling, in GB, for each node in a cluster. This number is limited between 2560 (2.5TiB) and 5120 (5TiB) for a SSD cluster and between 8192 (8TiB) and 16384 (16 TiB) for an HDD cluster. If not set, whatever is already set for the cluster will not change, or if the cluster is just being created, it will use the default value of 2560 for SSD clusters and 8192 for HDD clusters.
!> Warning: Only one of
autoscaling_config
ornum_nodes
should be set for a cluster. If both are set,num_nodes
is ignored. If none is set, autoscaling will be disabled and sized to the current node count.
- Cpu
Target int The target CPU utilization for autoscaling, in percentage. Must be between 10 and 80.
- Max
Nodes int The maximum number of nodes for autoscaling.
- Min
Nodes int The minimum number of nodes for autoscaling.
- Storage
Target int The target storage utilization for autoscaling, in GB, for each node in a cluster. This number is limited between 2560 (2.5TiB) and 5120 (5TiB) for a SSD cluster and between 8192 (8TiB) and 16384 (16 TiB) for an HDD cluster. If not set, whatever is already set for the cluster will not change, or if the cluster is just being created, it will use the default value of 2560 for SSD clusters and 8192 for HDD clusters.
!> Warning: Only one of
autoscaling_config
ornum_nodes
should be set for a cluster. If both are set,num_nodes
is ignored. If none is set, autoscaling will be disabled and sized to the current node count.
- cpu
Target Integer The target CPU utilization for autoscaling, in percentage. Must be between 10 and 80.
- max
Nodes Integer The maximum number of nodes for autoscaling.
- min
Nodes Integer The minimum number of nodes for autoscaling.
- storage
Target Integer The target storage utilization for autoscaling, in GB, for each node in a cluster. This number is limited between 2560 (2.5TiB) and 5120 (5TiB) for a SSD cluster and between 8192 (8TiB) and 16384 (16 TiB) for an HDD cluster. If not set, whatever is already set for the cluster will not change, or if the cluster is just being created, it will use the default value of 2560 for SSD clusters and 8192 for HDD clusters.
!> Warning: Only one of
autoscaling_config
ornum_nodes
should be set for a cluster. If both are set,num_nodes
is ignored. If none is set, autoscaling will be disabled and sized to the current node count.
- cpu
Target number The target CPU utilization for autoscaling, in percentage. Must be between 10 and 80.
- max
Nodes number The maximum number of nodes for autoscaling.
- min
Nodes number The minimum number of nodes for autoscaling.
- storage
Target number The target storage utilization for autoscaling, in GB, for each node in a cluster. This number is limited between 2560 (2.5TiB) and 5120 (5TiB) for a SSD cluster and between 8192 (8TiB) and 16384 (16 TiB) for an HDD cluster. If not set, whatever is already set for the cluster will not change, or if the cluster is just being created, it will use the default value of 2560 for SSD clusters and 8192 for HDD clusters.
!> Warning: Only one of
autoscaling_config
ornum_nodes
should be set for a cluster. If both are set,num_nodes
is ignored. If none is set, autoscaling will be disabled and sized to the current node count.
- cpu_
target int The target CPU utilization for autoscaling, in percentage. Must be between 10 and 80.
- max_
nodes int The maximum number of nodes for autoscaling.
- min_
nodes int The minimum number of nodes for autoscaling.
- storage_
target int The target storage utilization for autoscaling, in GB, for each node in a cluster. This number is limited between 2560 (2.5TiB) and 5120 (5TiB) for a SSD cluster and between 8192 (8TiB) and 16384 (16 TiB) for an HDD cluster. If not set, whatever is already set for the cluster will not change, or if the cluster is just being created, it will use the default value of 2560 for SSD clusters and 8192 for HDD clusters.
!> Warning: Only one of
autoscaling_config
ornum_nodes
should be set for a cluster. If both are set,num_nodes
is ignored. If none is set, autoscaling will be disabled and sized to the current node count.
- cpu
Target Number The target CPU utilization for autoscaling, in percentage. Must be between 10 and 80.
- max
Nodes Number The maximum number of nodes for autoscaling.
- min
Nodes Number The minimum number of nodes for autoscaling.
- storage
Target Number The target storage utilization for autoscaling, in GB, for each node in a cluster. This number is limited between 2560 (2.5TiB) and 5120 (5TiB) for a SSD cluster and between 8192 (8TiB) and 16384 (16 TiB) for an HDD cluster. If not set, whatever is already set for the cluster will not change, or if the cluster is just being created, it will use the default value of 2560 for SSD clusters and 8192 for HDD clusters.
!> Warning: Only one of
autoscaling_config
ornum_nodes
should be set for a cluster. If both are set,num_nodes
is ignored. If none is set, autoscaling will be disabled and sized to the current node count.
Import
Bigtable Instances can be imported using any of these accepted formats
$ pulumi import gcp:bigtable/instance:Instance default projects/{{project}}/instances/{{name}}
$ pulumi import gcp:bigtable/instance:Instance default {{project}}/{{name}}
$ pulumi import gcp:bigtable/instance:Instance default {{name}}
Package Details
- Repository
- Google Cloud (GCP) Classic pulumi/pulumi-gcp
- License
- Apache-2.0
- Notes
This Pulumi package is based on the
google-beta
Terraform Provider.