AppProfileState constructor

const AppProfileState({
  1. Input<String?>? appProfileId,
  2. Input<AppProfileDataBoostIsolationReadOnly?>? dataBoostIsolationReadOnly,
  3. Input<String?>? deletionPolicy,
  4. Input<String?>? description,
  5. Input<bool?>? ignoreWarnings,
  6. Input<String?>? instance,
  7. Input<List<String>?>? multiClusterRoutingClusterIds,
  8. Input<bool?>? multiClusterRoutingUseAny,
  9. Input<String?>? name,
  10. Input<String?>? project,
  11. Input<bool?>? rowAffinity,
  12. Input<AppProfileSingleClusterRouting?>? singleClusterRouting,
  13. Input<AppProfileStandardIsolation?>? standardIsolation,
})

Creates a new AppProfileState. appProfileId The unique name of the app profile in the form [_a-zA-Z0-9][-_.a-zA-Z0-9]*. dataBoostIsolationReadOnly Specifies that this app profile is intended for read-only usage via the Data Boost feature. deletionPolicy Whether Terraform will be prevented from destroying the resource. Defaults to DELETE. description Long form description of the use case for this app profile. ignoreWarnings If true, ignore safety checks when deleting/updating the app profile. instance The name of the instance to create the app profile within. multiClusterRoutingClusterIds The set of clusters to route to. The order is ignored; clusters will be tried in order of distance. If left empty, all clusters are eligible. multiClusterRoutingUseAny If true, read/write requests are routed to the nearest cluster in the instance, and will fail over to the nearest cluster that is available name The unique name of the requested app profile. Values are of the form projects/&lt;project&gt;/instances/&lt;instance&gt;/appProfiles/&lt;appProfileId&gt;. project The ID of the project in which the resource belongs. rowAffinity Must be used with multi-cluster routing. If true, then this app profile will use row affinity sticky routing. With row affinity, Bigtable will route single row key requests based on the row key, rather than randomly. Instead, each row key will be assigned to a cluster by Cloud Bigtable, and will stick to that cluster. Choosing this option improves read-your-writes consistency for most requests under most circumstances, without sacrificing availability. Consistency is not guaranteed, as requests may still fail over between clusters in the event of errors or latency. singleClusterRouting Use a single-cluster routing policy. standardIsolation The standard options used for isolating this app profile's traffic from other use cases.

Implementation

const AppProfileState({
  this.appProfileId,
  this.dataBoostIsolationReadOnly,
  this.deletionPolicy,
  this.description,
  this.ignoreWarnings,
  this.instance,
  this.multiClusterRoutingClusterIds,
  this.multiClusterRoutingUseAny,
  this.name,
  this.project,
  this.rowAffinity,
  this.singleClusterRouting,
  this.standardIsolation,
});