Docs Home Pulumi IaC Pulumi ESC Pulumi Cloud Packages Tutorials
  1. Packages
  2. Google Cloud Native
  3. API Docs
  4. healthcare
  5. healthcare/v1
  6. DicomStore

Google Cloud Native is in preview. Google Cloud Classic is fully supported.

Google Cloud Native v0.32.0 published on Wednesday, Nov 29, 2023 by Pulumi
pulumi/pulumi-google-native

google-native.healthcare/v1.DicomStore

Explore with Pulumi AI

google-native logo

Google Cloud Native is in preview. Google Cloud Classic is fully supported.

Google Cloud Native v0.32.0 published on Wednesday, Nov 29, 2023 by Pulumi
pulumi/pulumi-google-native

    Creates a new DICOM store within the parent dataset.

    Create DicomStore Resource

    Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.

    Constructor syntax

    new DicomStore(name: string, args: DicomStoreArgs, opts?: CustomResourceOptions);
    @overload
def DicomStore(resource_name: str,
               args: DicomStoreArgs,
               opts: Optional[ResourceOptions] = None)

@overload
def DicomStore(resource_name: str,
               opts: Optional[ResourceOptions] = None,
               dataset_id: Optional[str] = None,
               dicom_store_id: Optional[str] = None,
               labels: Optional[Mapping[str, str]] = None,
               location: Optional[str] = None,
               name: Optional[str] = None,
               notification_config: Optional[NotificationConfigArgs] = None,
               project: Optional[str] = None,
               stream_configs: Optional[Sequence[GoogleCloudHealthcareV1DicomStreamConfigArgs]] = None)
    func NewDicomStore(ctx *Context, name string, args DicomStoreArgs, opts ...ResourceOption) (*DicomStore, error)
    public DicomStore(string name, DicomStoreArgs args, CustomResourceOptions? opts = null)
    public DicomStore(String name, DicomStoreArgs args)
public DicomStore(String name, DicomStoreArgs args, CustomResourceOptions options)

    type: google-native:healthcare/v1:DicomStore
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.

    Parameters

    name string
    The unique name of the resource.
    args DicomStoreArgs
    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 DicomStoreArgs
    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 DicomStoreArgs
    The arguments to resource properties.
    opts ResourceOption
    Bag of options to control resource's behavior.
    name string
    The unique name of the resource.
    args DicomStoreArgs
    The arguments to resource properties.
    opts CustomResourceOptions
    Bag of options to control resource's behavior.
    name String
    The unique name of the resource.
    args DicomStoreArgs
    The arguments to resource properties.
    options CustomResourceOptions
    Bag of options to control resource's behavior.

    Constructor example

    The following reference example uses placeholder values for all input properties.

    var dicomStoreResource = new GoogleNative.Healthcare.V1.DicomStore("dicomStoreResource", new()
{
    DatasetId = "string",
    DicomStoreId = "string",
    Labels = 
    {
        { "string", "string" },
    },
    Location = "string",
    Name = "string",
    NotificationConfig = new GoogleNative.Healthcare.V1.Inputs.NotificationConfigArgs
    {
        PubsubTopic = "string",
        SendForBulkImport = false,
    },
    Project = "string",
    StreamConfigs = new[]
    {
        new GoogleNative.Healthcare.V1.Inputs.GoogleCloudHealthcareV1DicomStreamConfigArgs
        {
            BigqueryDestination = new GoogleNative.Healthcare.V1.Inputs.GoogleCloudHealthcareV1DicomBigQueryDestinationArgs
            {
                Force = false,
                TableUri = "string",
                WriteDisposition = GoogleNative.Healthcare.V1.GoogleCloudHealthcareV1DicomBigQueryDestinationWriteDisposition.WriteDispositionUnspecified,
            },
        },
    },
});

    example, err := healthcare.NewDicomStore(ctx, "dicomStoreResource", &healthcare.DicomStoreArgs{
	DatasetId:    pulumi.String("string"),
	DicomStoreId: pulumi.String("string"),
	Labels: pulumi.StringMap{
		"string": pulumi.String("string"),
	},
	Location: pulumi.String("string"),
	Name:     pulumi.String("string"),
	NotificationConfig: &healthcare.NotificationConfigArgs{
		PubsubTopic:       pulumi.String("string"),
		SendForBulkImport: pulumi.Bool(false),
	},
	Project: pulumi.String("string"),
	StreamConfigs: healthcare.GoogleCloudHealthcareV1DicomStreamConfigArray{
		&healthcare.GoogleCloudHealthcareV1DicomStreamConfigArgs{
			BigqueryDestination: &healthcare.GoogleCloudHealthcareV1DicomBigQueryDestinationArgs{
				Force:            pulumi.Bool(false),
				TableUri:         pulumi.String("string"),
				WriteDisposition: healthcare.GoogleCloudHealthcareV1DicomBigQueryDestinationWriteDispositionWriteDispositionUnspecified,
			},
		},
	},
})

    var dicomStoreResource = new DicomStore("dicomStoreResource", DicomStoreArgs.builder()
    .datasetId("string")
    .dicomStoreId("string")
    .labels(Map.of("string", "string"))
    .location("string")
    .name("string")
    .notificationConfig(NotificationConfigArgs.builder()
        .pubsubTopic("string")
        .sendForBulkImport(false)
        .build())
    .project("string")
    .streamConfigs(GoogleCloudHealthcareV1DicomStreamConfigArgs.builder()
        .bigqueryDestination(GoogleCloudHealthcareV1DicomBigQueryDestinationArgs.builder()
            .force(false)
            .tableUri("string")
            .writeDisposition("WRITE_DISPOSITION_UNSPECIFIED")
            .build())
        .build())
    .build());

    dicom_store_resource = google_native.healthcare.v1.DicomStore("dicomStoreResource",
    dataset_id="string",
    dicom_store_id="string",
    labels={
        "string": "string",
    },
    location="string",
    name="string",
    notification_config={
        "pubsub_topic": "string",
        "send_for_bulk_import": False,
    },
    project="string",
    stream_configs=[{
        "bigquery_destination": {
            "force": False,
            "table_uri": "string",
            "write_disposition": google_native.healthcare.v1.GoogleCloudHealthcareV1DicomBigQueryDestinationWriteDisposition.WRITE_DISPOSITION_UNSPECIFIED,
        },
    }])

    const dicomStoreResource = new google_native.healthcare.v1.DicomStore("dicomStoreResource", {
    datasetId: "string",
    dicomStoreId: "string",
    labels: {
        string: "string",
    },
    location: "string",
    name: "string",
    notificationConfig: {
        pubsubTopic: "string",
        sendForBulkImport: false,
    },
    project: "string",
    streamConfigs: [{
        bigqueryDestination: {
            force: false,
            tableUri: "string",
            writeDisposition: google_native.healthcare.v1.GoogleCloudHealthcareV1DicomBigQueryDestinationWriteDisposition.WriteDispositionUnspecified,
        },
    }],
});

    type: google-native:healthcare/v1:DicomStore
properties:
    datasetId: string
    dicomStoreId: string
    labels:
        string: string
    location: string
    name: string
    notificationConfig:
        pubsubTopic: string
        sendForBulkImport: false
    project: string
    streamConfigs:
        - bigqueryDestination:
            force: false
            tableUri: string
            writeDisposition: WRITE_DISPOSITION_UNSPECIFIED

    DicomStore Resource Properties

    To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.

    Inputs

    In Python, inputs that are objects can be passed either as argument classes or as dictionary literals.

    The DicomStore resource accepts the following input properties:

    DatasetId string
    DicomStoreId string
    The ID of the DICOM store that is being created. Any string value up to 256 characters in length.
    Labels Dictionary<string, string>
    User-supplied key-value pairs used to organize DICOM stores. Label keys must be between 1 and 63 characters long, have a UTF-8 encoding of maximum 128 bytes, and must conform to the following PCRE regular expression: \p{Ll}\p{Lo}{0,62} Label values are optional, must be between 1 and 63 characters long, have a UTF-8 encoding of maximum 128 bytes, and must conform to the following PCRE regular expression: [\p{Ll}\p{Lo}\p{N}_-]{0,63} No more than 64 labels can be associated with a given store.
    Location string
    Name string
    Resource name of the DICOM store, of the form projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/dicomStores/{dicom_store_id}.
    NotificationConfig Pulumi.GoogleNative.Healthcare.V1.Inputs.NotificationConfig
    Notification destination for new DICOM instances. Supplied by the client.
    Project string
    StreamConfigs List<Pulumi.GoogleNative.Healthcare.V1.Inputs.GoogleCloudHealthcareV1DicomStreamConfig>
    Optional. A list of streaming configs used to configure the destination of streaming exports for every DICOM instance insertion in this DICOM store. After a new config is added to stream_configs, DICOM instance insertions are streamed to the new destination. When a config is removed from stream_configs, the server stops streaming to that destination. Each config must contain a unique destination.
    DatasetId string
    DicomStoreId string
    The ID of the DICOM store that is being created. Any string value up to 256 characters in length.
    Labels map[string]string
    User-supplied key-value pairs used to organize DICOM stores. Label keys must be between 1 and 63 characters long, have a UTF-8 encoding of maximum 128 bytes, and must conform to the following PCRE regular expression: \p{Ll}\p{Lo}{0,62} Label values are optional, must be between 1 and 63 characters long, have a UTF-8 encoding of maximum 128 bytes, and must conform to the following PCRE regular expression: [\p{Ll}\p{Lo}\p{N}_-]{0,63} No more than 64 labels can be associated with a given store.
    Location string
    Name string
    Resource name of the DICOM store, of the form projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/dicomStores/{dicom_store_id}.
    NotificationConfig NotificationConfigArgs
    Notification destination for new DICOM instances. Supplied by the client.
    Project string
    StreamConfigs []GoogleCloudHealthcareV1DicomStreamConfigArgs
    Optional. A list of streaming configs used to configure the destination of streaming exports for every DICOM instance insertion in this DICOM store. After a new config is added to stream_configs, DICOM instance insertions are streamed to the new destination. When a config is removed from stream_configs, the server stops streaming to that destination. Each config must contain a unique destination.
    datasetId String
    dicomStoreId String
    The ID of the DICOM store that is being created. Any string value up to 256 characters in length.
    labels Map<String,String>
    User-supplied key-value pairs used to organize DICOM stores. Label keys must be between 1 and 63 characters long, have a UTF-8 encoding of maximum 128 bytes, and must conform to the following PCRE regular expression: \p{Ll}\p{Lo}{0,62} Label values are optional, must be between 1 and 63 characters long, have a UTF-8 encoding of maximum 128 bytes, and must conform to the following PCRE regular expression: [\p{Ll}\p{Lo}\p{N}_-]{0,63} No more than 64 labels can be associated with a given store.
    location String
    name String
    Resource name of the DICOM store, of the form projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/dicomStores/{dicom_store_id}.
    notificationConfig NotificationConfig
    Notification destination for new DICOM instances. Supplied by the client.
    project String
    streamConfigs List<GoogleCloudHealthcareV1DicomStreamConfig>
    Optional. A list of streaming configs used to configure the destination of streaming exports for every DICOM instance insertion in this DICOM store. After a new config is added to stream_configs, DICOM instance insertions are streamed to the new destination. When a config is removed from stream_configs, the server stops streaming to that destination. Each config must contain a unique destination.
    datasetId string
    dicomStoreId string
    The ID of the DICOM store that is being created. Any string value up to 256 characters in length.
    labels {[key: string]: string}
    User-supplied key-value pairs used to organize DICOM stores. Label keys must be between 1 and 63 characters long, have a UTF-8 encoding of maximum 128 bytes, and must conform to the following PCRE regular expression: \p{Ll}\p{Lo}{0,62} Label values are optional, must be between 1 and 63 characters long, have a UTF-8 encoding of maximum 128 bytes, and must conform to the following PCRE regular expression: [\p{Ll}\p{Lo}\p{N}_-]{0,63} No more than 64 labels can be associated with a given store.
    location string
    name string
    Resource name of the DICOM store, of the form projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/dicomStores/{dicom_store_id}.
    notificationConfig NotificationConfig
    Notification destination for new DICOM instances. Supplied by the client.
    project string
    streamConfigs GoogleCloudHealthcareV1DicomStreamConfig[]
    Optional. A list of streaming configs used to configure the destination of streaming exports for every DICOM instance insertion in this DICOM store. After a new config is added to stream_configs, DICOM instance insertions are streamed to the new destination. When a config is removed from stream_configs, the server stops streaming to that destination. Each config must contain a unique destination.
    dataset_id str
    dicom_store_id str
    The ID of the DICOM store that is being created. Any string value up to 256 characters in length.
    labels Mapping[str, str]
    User-supplied key-value pairs used to organize DICOM stores. Label keys must be between 1 and 63 characters long, have a UTF-8 encoding of maximum 128 bytes, and must conform to the following PCRE regular expression: \p{Ll}\p{Lo}{0,62} Label values are optional, must be between 1 and 63 characters long, have a UTF-8 encoding of maximum 128 bytes, and must conform to the following PCRE regular expression: [\p{Ll}\p{Lo}\p{N}_-]{0,63} No more than 64 labels can be associated with a given store.
    location str
    name str
    Resource name of the DICOM store, of the form projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/dicomStores/{dicom_store_id}.
    notification_config NotificationConfigArgs
    Notification destination for new DICOM instances. Supplied by the client.
    project str
    stream_configs Sequence[GoogleCloudHealthcareV1DicomStreamConfigArgs]
    Optional. A list of streaming configs used to configure the destination of streaming exports for every DICOM instance insertion in this DICOM store. After a new config is added to stream_configs, DICOM instance insertions are streamed to the new destination. When a config is removed from stream_configs, the server stops streaming to that destination. Each config must contain a unique destination.
    datasetId String
    dicomStoreId String
    The ID of the DICOM store that is being created. Any string value up to 256 characters in length.
    labels Map<String>
    User-supplied key-value pairs used to organize DICOM stores. Label keys must be between 1 and 63 characters long, have a UTF-8 encoding of maximum 128 bytes, and must conform to the following PCRE regular expression: \p{Ll}\p{Lo}{0,62} Label values are optional, must be between 1 and 63 characters long, have a UTF-8 encoding of maximum 128 bytes, and must conform to the following PCRE regular expression: [\p{Ll}\p{Lo}\p{N}_-]{0,63} No more than 64 labels can be associated with a given store.
    location String
    name String
    Resource name of the DICOM store, of the form projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/dicomStores/{dicom_store_id}.
    notificationConfig Property Map
    Notification destination for new DICOM instances. Supplied by the client.
    project String
    streamConfigs List<Property Map>
    Optional. A list of streaming configs used to configure the destination of streaming exports for every DICOM instance insertion in this DICOM store. After a new config is added to stream_configs, DICOM instance insertions are streamed to the new destination. When a config is removed from stream_configs, the server stops streaming to that destination. Each config must contain a unique destination.

    Outputs

    All input properties are implicitly available as output properties. Additionally, the DicomStore 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.

    Supporting Types

    GoogleCloudHealthcareV1DicomBigQueryDestination, GoogleCloudHealthcareV1DicomBigQueryDestinationArgs

    Force bool
    Use write_disposition instead. If write_disposition is specified, this parameter is ignored. force=false is equivalent to write_disposition=WRITE_EMPTY and force=true is equivalent to write_disposition=WRITE_TRUNCATE.
    TableUri string
    BigQuery URI to a table, up to 2000 characters long, in the format bq://projectId.bqDatasetId.tableId
    WriteDisposition Pulumi.GoogleNative.Healthcare.V1.GoogleCloudHealthcareV1DicomBigQueryDestinationWriteDisposition
    Determines whether the existing table in the destination is to be overwritten or appended to. If a write_disposition is specified, the force parameter is ignored.
    Force bool
    Use write_disposition instead. If write_disposition is specified, this parameter is ignored. force=false is equivalent to write_disposition=WRITE_EMPTY and force=true is equivalent to write_disposition=WRITE_TRUNCATE.
    TableUri string
    BigQuery URI to a table, up to 2000 characters long, in the format bq://projectId.bqDatasetId.tableId
    WriteDisposition GoogleCloudHealthcareV1DicomBigQueryDestinationWriteDisposition
    Determines whether the existing table in the destination is to be overwritten or appended to. If a write_disposition is specified, the force parameter is ignored.
    force Boolean
    Use write_disposition instead. If write_disposition is specified, this parameter is ignored. force=false is equivalent to write_disposition=WRITE_EMPTY and force=true is equivalent to write_disposition=WRITE_TRUNCATE.
    tableUri String
    BigQuery URI to a table, up to 2000 characters long, in the format bq://projectId.bqDatasetId.tableId
    writeDisposition GoogleCloudHealthcareV1DicomBigQueryDestinationWriteDisposition
    Determines whether the existing table in the destination is to be overwritten or appended to. If a write_disposition is specified, the force parameter is ignored.
    force boolean
    Use write_disposition instead. If write_disposition is specified, this parameter is ignored. force=false is equivalent to write_disposition=WRITE_EMPTY and force=true is equivalent to write_disposition=WRITE_TRUNCATE.
    tableUri string
    BigQuery URI to a table, up to 2000 characters long, in the format bq://projectId.bqDatasetId.tableId
    writeDisposition GoogleCloudHealthcareV1DicomBigQueryDestinationWriteDisposition
    Determines whether the existing table in the destination is to be overwritten or appended to. If a write_disposition is specified, the force parameter is ignored.
    force bool
    Use write_disposition instead. If write_disposition is specified, this parameter is ignored. force=false is equivalent to write_disposition=WRITE_EMPTY and force=true is equivalent to write_disposition=WRITE_TRUNCATE.
    table_uri str
    BigQuery URI to a table, up to 2000 characters long, in the format bq://projectId.bqDatasetId.tableId
    write_disposition GoogleCloudHealthcareV1DicomBigQueryDestinationWriteDisposition
    Determines whether the existing table in the destination is to be overwritten or appended to. If a write_disposition is specified, the force parameter is ignored.
    force Boolean
    Use write_disposition instead. If write_disposition is specified, this parameter is ignored. force=false is equivalent to write_disposition=WRITE_EMPTY and force=true is equivalent to write_disposition=WRITE_TRUNCATE.
    tableUri String
    BigQuery URI to a table, up to 2000 characters long, in the format bq://projectId.bqDatasetId.tableId
    writeDisposition "WRITE_DISPOSITION_UNSPECIFIED" | "WRITE_EMPTY" | "WRITE_TRUNCATE" | "WRITE_APPEND"
    Determines whether the existing table in the destination is to be overwritten or appended to. If a write_disposition is specified, the force parameter is ignored.

    GoogleCloudHealthcareV1DicomBigQueryDestinationResponse, GoogleCloudHealthcareV1DicomBigQueryDestinationResponseArgs

    Force bool
    Use write_disposition instead. If write_disposition is specified, this parameter is ignored. force=false is equivalent to write_disposition=WRITE_EMPTY and force=true is equivalent to write_disposition=WRITE_TRUNCATE.
    TableUri string
    BigQuery URI to a table, up to 2000 characters long, in the format bq://projectId.bqDatasetId.tableId
    WriteDisposition string
    Determines whether the existing table in the destination is to be overwritten or appended to. If a write_disposition is specified, the force parameter is ignored.
    Force bool
    Use write_disposition instead. If write_disposition is specified, this parameter is ignored. force=false is equivalent to write_disposition=WRITE_EMPTY and force=true is equivalent to write_disposition=WRITE_TRUNCATE.
    TableUri string
    BigQuery URI to a table, up to 2000 characters long, in the format bq://projectId.bqDatasetId.tableId
    WriteDisposition string
    Determines whether the existing table in the destination is to be overwritten or appended to. If a write_disposition is specified, the force parameter is ignored.
    force Boolean
    Use write_disposition instead. If write_disposition is specified, this parameter is ignored. force=false is equivalent to write_disposition=WRITE_EMPTY and force=true is equivalent to write_disposition=WRITE_TRUNCATE.
    tableUri String
    BigQuery URI to a table, up to 2000 characters long, in the format bq://projectId.bqDatasetId.tableId
    writeDisposition String
    Determines whether the existing table in the destination is to be overwritten or appended to. If a write_disposition is specified, the force parameter is ignored.
    force boolean
    Use write_disposition instead. If write_disposition is specified, this parameter is ignored. force=false is equivalent to write_disposition=WRITE_EMPTY and force=true is equivalent to write_disposition=WRITE_TRUNCATE.
    tableUri string
    BigQuery URI to a table, up to 2000 characters long, in the format bq://projectId.bqDatasetId.tableId
    writeDisposition string
    Determines whether the existing table in the destination is to be overwritten or appended to. If a write_disposition is specified, the force parameter is ignored.
    force bool
    Use write_disposition instead. If write_disposition is specified, this parameter is ignored. force=false is equivalent to write_disposition=WRITE_EMPTY and force=true is equivalent to write_disposition=WRITE_TRUNCATE.
    table_uri str
    BigQuery URI to a table, up to 2000 characters long, in the format bq://projectId.bqDatasetId.tableId
    write_disposition str
    Determines whether the existing table in the destination is to be overwritten or appended to. If a write_disposition is specified, the force parameter is ignored.
    force Boolean
    Use write_disposition instead. If write_disposition is specified, this parameter is ignored. force=false is equivalent to write_disposition=WRITE_EMPTY and force=true is equivalent to write_disposition=WRITE_TRUNCATE.
    tableUri String
    BigQuery URI to a table, up to 2000 characters long, in the format bq://projectId.bqDatasetId.tableId
    writeDisposition String
    Determines whether the existing table in the destination is to be overwritten or appended to. If a write_disposition is specified, the force parameter is ignored.

    GoogleCloudHealthcareV1DicomBigQueryDestinationWriteDisposition, GoogleCloudHealthcareV1DicomBigQueryDestinationWriteDispositionArgs

    WriteDispositionUnspecified
    WRITE_DISPOSITION_UNSPECIFIEDDefault behavior is the same as WRITE_EMPTY.
    WriteEmpty
    WRITE_EMPTYOnly export data if the destination table is empty.
    WriteTruncate
    WRITE_TRUNCATEErase all existing data in the destination table before writing the instances.
    WriteAppend
    WRITE_APPENDAppend data to the destination table.
    GoogleCloudHealthcareV1DicomBigQueryDestinationWriteDispositionWriteDispositionUnspecified
    WRITE_DISPOSITION_UNSPECIFIEDDefault behavior is the same as WRITE_EMPTY.
    GoogleCloudHealthcareV1DicomBigQueryDestinationWriteDispositionWriteEmpty
    WRITE_EMPTYOnly export data if the destination table is empty.
    GoogleCloudHealthcareV1DicomBigQueryDestinationWriteDispositionWriteTruncate
    WRITE_TRUNCATEErase all existing data in the destination table before writing the instances.
    GoogleCloudHealthcareV1DicomBigQueryDestinationWriteDispositionWriteAppend
    WRITE_APPENDAppend data to the destination table.
    WriteDispositionUnspecified
    WRITE_DISPOSITION_UNSPECIFIEDDefault behavior is the same as WRITE_EMPTY.
    WriteEmpty
    WRITE_EMPTYOnly export data if the destination table is empty.
    WriteTruncate
    WRITE_TRUNCATEErase all existing data in the destination table before writing the instances.
    WriteAppend
    WRITE_APPENDAppend data to the destination table.
    WriteDispositionUnspecified
    WRITE_DISPOSITION_UNSPECIFIEDDefault behavior is the same as WRITE_EMPTY.
    WriteEmpty
    WRITE_EMPTYOnly export data if the destination table is empty.
    WriteTruncate
    WRITE_TRUNCATEErase all existing data in the destination table before writing the instances.
    WriteAppend
    WRITE_APPENDAppend data to the destination table.
    WRITE_DISPOSITION_UNSPECIFIED
    WRITE_DISPOSITION_UNSPECIFIEDDefault behavior is the same as WRITE_EMPTY.
    WRITE_EMPTY
    WRITE_EMPTYOnly export data if the destination table is empty.
    WRITE_TRUNCATE
    WRITE_TRUNCATEErase all existing data in the destination table before writing the instances.
    WRITE_APPEND
    WRITE_APPENDAppend data to the destination table.
    "WRITE_DISPOSITION_UNSPECIFIED"
    WRITE_DISPOSITION_UNSPECIFIEDDefault behavior is the same as WRITE_EMPTY.
    "WRITE_EMPTY"
    WRITE_EMPTYOnly export data if the destination table is empty.
    "WRITE_TRUNCATE"
    WRITE_TRUNCATEErase all existing data in the destination table before writing the instances.
    "WRITE_APPEND"
    WRITE_APPENDAppend data to the destination table.

    GoogleCloudHealthcareV1DicomStreamConfig, GoogleCloudHealthcareV1DicomStreamConfigArgs

    BigqueryDestination Pulumi.GoogleNative.Healthcare.V1.Inputs.GoogleCloudHealthcareV1DicomBigQueryDestination
    Results are appended to this table. The server creates a new table in the given BigQuery dataset if the specified table does not exist. To enable the Cloud Healthcare API to write to your BigQuery table, you must give the Cloud Healthcare API service account the bigquery.dataEditor role. The service account is: service-{PROJECT_NUMBER}@gcp-sa-healthcare.iam.gserviceaccount.com. The PROJECT_NUMBER identifies the project that the DICOM store resides in. To get the project number, go to the Cloud Console Dashboard. It is recommended to not have a custom schema in the destination table which could conflict with the schema created by the Cloud Healthcare API. Instance deletions are not applied to the destination table. The destination's table schema will be automatically updated in case a new instance's data is incompatible with the current schema. The schema should not be updated manually as this can cause incompatibilies that cannot be resolved automatically. One resolution in this case is to delete the incompatible table and let the server recreate one, though the newly created table only contains data after the table recreation. BigQuery imposes a 1 MB limit on streaming insert row size, therefore any instance that generates more than 1 MB of BigQuery data will not be streamed. If an instance cannot be streamed to BigQuery, errors will be logged to Cloud Logging (see Viewing error logs in Cloud Logging).
    BigqueryDestination GoogleCloudHealthcareV1DicomBigQueryDestination
    Results are appended to this table. The server creates a new table in the given BigQuery dataset if the specified table does not exist. To enable the Cloud Healthcare API to write to your BigQuery table, you must give the Cloud Healthcare API service account the bigquery.dataEditor role. The service account is: service-{PROJECT_NUMBER}@gcp-sa-healthcare.iam.gserviceaccount.com. The PROJECT_NUMBER identifies the project that the DICOM store resides in. To get the project number, go to the Cloud Console Dashboard. It is recommended to not have a custom schema in the destination table which could conflict with the schema created by the Cloud Healthcare API. Instance deletions are not applied to the destination table. The destination's table schema will be automatically updated in case a new instance's data is incompatible with the current schema. The schema should not be updated manually as this can cause incompatibilies that cannot be resolved automatically. One resolution in this case is to delete the incompatible table and let the server recreate one, though the newly created table only contains data after the table recreation. BigQuery imposes a 1 MB limit on streaming insert row size, therefore any instance that generates more than 1 MB of BigQuery data will not be streamed. If an instance cannot be streamed to BigQuery, errors will be logged to Cloud Logging (see Viewing error logs in Cloud Logging).
    bigqueryDestination GoogleCloudHealthcareV1DicomBigQueryDestination
    Results are appended to this table. The server creates a new table in the given BigQuery dataset if the specified table does not exist. To enable the Cloud Healthcare API to write to your BigQuery table, you must give the Cloud Healthcare API service account the bigquery.dataEditor role. The service account is: service-{PROJECT_NUMBER}@gcp-sa-healthcare.iam.gserviceaccount.com. The PROJECT_NUMBER identifies the project that the DICOM store resides in. To get the project number, go to the Cloud Console Dashboard. It is recommended to not have a custom schema in the destination table which could conflict with the schema created by the Cloud Healthcare API. Instance deletions are not applied to the destination table. The destination's table schema will be automatically updated in case a new instance's data is incompatible with the current schema. The schema should not be updated manually as this can cause incompatibilies that cannot be resolved automatically. One resolution in this case is to delete the incompatible table and let the server recreate one, though the newly created table only contains data after the table recreation. BigQuery imposes a 1 MB limit on streaming insert row size, therefore any instance that generates more than 1 MB of BigQuery data will not be streamed. If an instance cannot be streamed to BigQuery, errors will be logged to Cloud Logging (see Viewing error logs in Cloud Logging).
    bigqueryDestination GoogleCloudHealthcareV1DicomBigQueryDestination
    Results are appended to this table. The server creates a new table in the given BigQuery dataset if the specified table does not exist. To enable the Cloud Healthcare API to write to your BigQuery table, you must give the Cloud Healthcare API service account the bigquery.dataEditor role. The service account is: service-{PROJECT_NUMBER}@gcp-sa-healthcare.iam.gserviceaccount.com. The PROJECT_NUMBER identifies the project that the DICOM store resides in. To get the project number, go to the Cloud Console Dashboard. It is recommended to not have a custom schema in the destination table which could conflict with the schema created by the Cloud Healthcare API. Instance deletions are not applied to the destination table. The destination's table schema will be automatically updated in case a new instance's data is incompatible with the current schema. The schema should not be updated manually as this can cause incompatibilies that cannot be resolved automatically. One resolution in this case is to delete the incompatible table and let the server recreate one, though the newly created table only contains data after the table recreation. BigQuery imposes a 1 MB limit on streaming insert row size, therefore any instance that generates more than 1 MB of BigQuery data will not be streamed. If an instance cannot be streamed to BigQuery, errors will be logged to Cloud Logging (see Viewing error logs in Cloud Logging).
    bigquery_destination GoogleCloudHealthcareV1DicomBigQueryDestination
    Results are appended to this table. The server creates a new table in the given BigQuery dataset if the specified table does not exist. To enable the Cloud Healthcare API to write to your BigQuery table, you must give the Cloud Healthcare API service account the bigquery.dataEditor role. The service account is: service-{PROJECT_NUMBER}@gcp-sa-healthcare.iam.gserviceaccount.com. The PROJECT_NUMBER identifies the project that the DICOM store resides in. To get the project number, go to the Cloud Console Dashboard. It is recommended to not have a custom schema in the destination table which could conflict with the schema created by the Cloud Healthcare API. Instance deletions are not applied to the destination table. The destination's table schema will be automatically updated in case a new instance's data is incompatible with the current schema. The schema should not be updated manually as this can cause incompatibilies that cannot be resolved automatically. One resolution in this case is to delete the incompatible table and let the server recreate one, though the newly created table only contains data after the table recreation. BigQuery imposes a 1 MB limit on streaming insert row size, therefore any instance that generates more than 1 MB of BigQuery data will not be streamed. If an instance cannot be streamed to BigQuery, errors will be logged to Cloud Logging (see Viewing error logs in Cloud Logging).
    bigqueryDestination Property Map
    Results are appended to this table. The server creates a new table in the given BigQuery dataset if the specified table does not exist. To enable the Cloud Healthcare API to write to your BigQuery table, you must give the Cloud Healthcare API service account the bigquery.dataEditor role. The service account is: service-{PROJECT_NUMBER}@gcp-sa-healthcare.iam.gserviceaccount.com. The PROJECT_NUMBER identifies the project that the DICOM store resides in. To get the project number, go to the Cloud Console Dashboard. It is recommended to not have a custom schema in the destination table which could conflict with the schema created by the Cloud Healthcare API. Instance deletions are not applied to the destination table. The destination's table schema will be automatically updated in case a new instance's data is incompatible with the current schema. The schema should not be updated manually as this can cause incompatibilies that cannot be resolved automatically. One resolution in this case is to delete the incompatible table and let the server recreate one, though the newly created table only contains data after the table recreation. BigQuery imposes a 1 MB limit on streaming insert row size, therefore any instance that generates more than 1 MB of BigQuery data will not be streamed. If an instance cannot be streamed to BigQuery, errors will be logged to Cloud Logging (see Viewing error logs in Cloud Logging).

    GoogleCloudHealthcareV1DicomStreamConfigResponse, GoogleCloudHealthcareV1DicomStreamConfigResponseArgs

    BigqueryDestination Pulumi.GoogleNative.Healthcare.V1.Inputs.GoogleCloudHealthcareV1DicomBigQueryDestinationResponse
    Results are appended to this table. The server creates a new table in the given BigQuery dataset if the specified table does not exist. To enable the Cloud Healthcare API to write to your BigQuery table, you must give the Cloud Healthcare API service account the bigquery.dataEditor role. The service account is: service-{PROJECT_NUMBER}@gcp-sa-healthcare.iam.gserviceaccount.com. The PROJECT_NUMBER identifies the project that the DICOM store resides in. To get the project number, go to the Cloud Console Dashboard. It is recommended to not have a custom schema in the destination table which could conflict with the schema created by the Cloud Healthcare API. Instance deletions are not applied to the destination table. The destination's table schema will be automatically updated in case a new instance's data is incompatible with the current schema. The schema should not be updated manually as this can cause incompatibilies that cannot be resolved automatically. One resolution in this case is to delete the incompatible table and let the server recreate one, though the newly created table only contains data after the table recreation. BigQuery imposes a 1 MB limit on streaming insert row size, therefore any instance that generates more than 1 MB of BigQuery data will not be streamed. If an instance cannot be streamed to BigQuery, errors will be logged to Cloud Logging (see Viewing error logs in Cloud Logging).
    BigqueryDestination GoogleCloudHealthcareV1DicomBigQueryDestinationResponse
    Results are appended to this table. The server creates a new table in the given BigQuery dataset if the specified table does not exist. To enable the Cloud Healthcare API to write to your BigQuery table, you must give the Cloud Healthcare API service account the bigquery.dataEditor role. The service account is: service-{PROJECT_NUMBER}@gcp-sa-healthcare.iam.gserviceaccount.com. The PROJECT_NUMBER identifies the project that the DICOM store resides in. To get the project number, go to the Cloud Console Dashboard. It is recommended to not have a custom schema in the destination table which could conflict with the schema created by the Cloud Healthcare API. Instance deletions are not applied to the destination table. The destination's table schema will be automatically updated in case a new instance's data is incompatible with the current schema. The schema should not be updated manually as this can cause incompatibilies that cannot be resolved automatically. One resolution in this case is to delete the incompatible table and let the server recreate one, though the newly created table only contains data after the table recreation. BigQuery imposes a 1 MB limit on streaming insert row size, therefore any instance that generates more than 1 MB of BigQuery data will not be streamed. If an instance cannot be streamed to BigQuery, errors will be logged to Cloud Logging (see Viewing error logs in Cloud Logging).
    bigqueryDestination GoogleCloudHealthcareV1DicomBigQueryDestinationResponse
    Results are appended to this table. The server creates a new table in the given BigQuery dataset if the specified table does not exist. To enable the Cloud Healthcare API to write to your BigQuery table, you must give the Cloud Healthcare API service account the bigquery.dataEditor role. The service account is: service-{PROJECT_NUMBER}@gcp-sa-healthcare.iam.gserviceaccount.com. The PROJECT_NUMBER identifies the project that the DICOM store resides in. To get the project number, go to the Cloud Console Dashboard. It is recommended to not have a custom schema in the destination table which could conflict with the schema created by the Cloud Healthcare API. Instance deletions are not applied to the destination table. The destination's table schema will be automatically updated in case a new instance's data is incompatible with the current schema. The schema should not be updated manually as this can cause incompatibilies that cannot be resolved automatically. One resolution in this case is to delete the incompatible table and let the server recreate one, though the newly created table only contains data after the table recreation. BigQuery imposes a 1 MB limit on streaming insert row size, therefore any instance that generates more than 1 MB of BigQuery data will not be streamed. If an instance cannot be streamed to BigQuery, errors will be logged to Cloud Logging (see Viewing error logs in Cloud Logging).
    bigqueryDestination GoogleCloudHealthcareV1DicomBigQueryDestinationResponse
    Results are appended to this table. The server creates a new table in the given BigQuery dataset if the specified table does not exist. To enable the Cloud Healthcare API to write to your BigQuery table, you must give the Cloud Healthcare API service account the bigquery.dataEditor role. The service account is: service-{PROJECT_NUMBER}@gcp-sa-healthcare.iam.gserviceaccount.com. The PROJECT_NUMBER identifies the project that the DICOM store resides in. To get the project number, go to the Cloud Console Dashboard. It is recommended to not have a custom schema in the destination table which could conflict with the schema created by the Cloud Healthcare API. Instance deletions are not applied to the destination table. The destination's table schema will be automatically updated in case a new instance's data is incompatible with the current schema. The schema should not be updated manually as this can cause incompatibilies that cannot be resolved automatically. One resolution in this case is to delete the incompatible table and let the server recreate one, though the newly created table only contains data after the table recreation. BigQuery imposes a 1 MB limit on streaming insert row size, therefore any instance that generates more than 1 MB of BigQuery data will not be streamed. If an instance cannot be streamed to BigQuery, errors will be logged to Cloud Logging (see Viewing error logs in Cloud Logging).
    bigquery_destination GoogleCloudHealthcareV1DicomBigQueryDestinationResponse
    Results are appended to this table. The server creates a new table in the given BigQuery dataset if the specified table does not exist. To enable the Cloud Healthcare API to write to your BigQuery table, you must give the Cloud Healthcare API service account the bigquery.dataEditor role. The service account is: service-{PROJECT_NUMBER}@gcp-sa-healthcare.iam.gserviceaccount.com. The PROJECT_NUMBER identifies the project that the DICOM store resides in. To get the project number, go to the Cloud Console Dashboard. It is recommended to not have a custom schema in the destination table which could conflict with the schema created by the Cloud Healthcare API. Instance deletions are not applied to the destination table. The destination's table schema will be automatically updated in case a new instance's data is incompatible with the current schema. The schema should not be updated manually as this can cause incompatibilies that cannot be resolved automatically. One resolution in this case is to delete the incompatible table and let the server recreate one, though the newly created table only contains data after the table recreation. BigQuery imposes a 1 MB limit on streaming insert row size, therefore any instance that generates more than 1 MB of BigQuery data will not be streamed. If an instance cannot be streamed to BigQuery, errors will be logged to Cloud Logging (see Viewing error logs in Cloud Logging).
    bigqueryDestination Property Map
    Results are appended to this table. The server creates a new table in the given BigQuery dataset if the specified table does not exist. To enable the Cloud Healthcare API to write to your BigQuery table, you must give the Cloud Healthcare API service account the bigquery.dataEditor role. The service account is: service-{PROJECT_NUMBER}@gcp-sa-healthcare.iam.gserviceaccount.com. The PROJECT_NUMBER identifies the project that the DICOM store resides in. To get the project number, go to the Cloud Console Dashboard. It is recommended to not have a custom schema in the destination table which could conflict with the schema created by the Cloud Healthcare API. Instance deletions are not applied to the destination table. The destination's table schema will be automatically updated in case a new instance's data is incompatible with the current schema. The schema should not be updated manually as this can cause incompatibilies that cannot be resolved automatically. One resolution in this case is to delete the incompatible table and let the server recreate one, though the newly created table only contains data after the table recreation. BigQuery imposes a 1 MB limit on streaming insert row size, therefore any instance that generates more than 1 MB of BigQuery data will not be streamed. If an instance cannot be streamed to BigQuery, errors will be logged to Cloud Logging (see Viewing error logs in Cloud Logging).

    NotificationConfig, NotificationConfigArgs

    PubsubTopic string
    The Pub/Sub topic that notifications of changes are published on. Supplied by the client. PubsubMessage.Data contains the resource name. PubsubMessage.MessageId is the ID of this message. It is guaranteed to be unique within the topic. PubsubMessage.PublishTime is the time at which the message was published. Notifications are only sent if the topic is non-empty. Topic names must be scoped to a project. Cloud Healthcare API service account must have publisher permissions on the given Pub/Sub topic. Not having adequate permissions causes the calls that send notifications to fail. If a notification can't be published to Pub/Sub, errors are logged to Cloud Logging (see Viewing error logs in Cloud Logging). If the number of errors exceeds a certain rate, some aren't submitted. Note that not all operations trigger notifications, see Configuring Pub/Sub notifications for specific details.
    SendForBulkImport bool
    Indicates whether or not to send Pub/Sub notifications on bulk import. Only supported for DICOM imports.
    PubsubTopic string
    The Pub/Sub topic that notifications of changes are published on. Supplied by the client. PubsubMessage.Data contains the resource name. PubsubMessage.MessageId is the ID of this message. It is guaranteed to be unique within the topic. PubsubMessage.PublishTime is the time at which the message was published. Notifications are only sent if the topic is non-empty. Topic names must be scoped to a project. Cloud Healthcare API service account must have publisher permissions on the given Pub/Sub topic. Not having adequate permissions causes the calls that send notifications to fail. If a notification can't be published to Pub/Sub, errors are logged to Cloud Logging (see Viewing error logs in Cloud Logging). If the number of errors exceeds a certain rate, some aren't submitted. Note that not all operations trigger notifications, see Configuring Pub/Sub notifications for specific details.
    SendForBulkImport bool
    Indicates whether or not to send Pub/Sub notifications on bulk import. Only supported for DICOM imports.
    pubsubTopic String
    The Pub/Sub topic that notifications of changes are published on. Supplied by the client. PubsubMessage.Data contains the resource name. PubsubMessage.MessageId is the ID of this message. It is guaranteed to be unique within the topic. PubsubMessage.PublishTime is the time at which the message was published. Notifications are only sent if the topic is non-empty. Topic names must be scoped to a project. Cloud Healthcare API service account must have publisher permissions on the given Pub/Sub topic. Not having adequate permissions causes the calls that send notifications to fail. If a notification can't be published to Pub/Sub, errors are logged to Cloud Logging (see Viewing error logs in Cloud Logging). If the number of errors exceeds a certain rate, some aren't submitted. Note that not all operations trigger notifications, see Configuring Pub/Sub notifications for specific details.
    sendForBulkImport Boolean
    Indicates whether or not to send Pub/Sub notifications on bulk import. Only supported for DICOM imports.
    pubsubTopic string
    The Pub/Sub topic that notifications of changes are published on. Supplied by the client. PubsubMessage.Data contains the resource name. PubsubMessage.MessageId is the ID of this message. It is guaranteed to be unique within the topic. PubsubMessage.PublishTime is the time at which the message was published. Notifications are only sent if the topic is non-empty. Topic names must be scoped to a project. Cloud Healthcare API service account must have publisher permissions on the given Pub/Sub topic. Not having adequate permissions causes the calls that send notifications to fail. If a notification can't be published to Pub/Sub, errors are logged to Cloud Logging (see Viewing error logs in Cloud Logging). If the number of errors exceeds a certain rate, some aren't submitted. Note that not all operations trigger notifications, see Configuring Pub/Sub notifications for specific details.
    sendForBulkImport boolean
    Indicates whether or not to send Pub/Sub notifications on bulk import. Only supported for DICOM imports.
    pubsub_topic str
    The Pub/Sub topic that notifications of changes are published on. Supplied by the client. PubsubMessage.Data contains the resource name. PubsubMessage.MessageId is the ID of this message. It is guaranteed to be unique within the topic. PubsubMessage.PublishTime is the time at which the message was published. Notifications are only sent if the topic is non-empty. Topic names must be scoped to a project. Cloud Healthcare API service account must have publisher permissions on the given Pub/Sub topic. Not having adequate permissions causes the calls that send notifications to fail. If a notification can't be published to Pub/Sub, errors are logged to Cloud Logging (see Viewing error logs in Cloud Logging). If the number of errors exceeds a certain rate, some aren't submitted. Note that not all operations trigger notifications, see Configuring Pub/Sub notifications for specific details.
    send_for_bulk_import bool
    Indicates whether or not to send Pub/Sub notifications on bulk import. Only supported for DICOM imports.
    pubsubTopic String
    The Pub/Sub topic that notifications of changes are published on. Supplied by the client. PubsubMessage.Data contains the resource name. PubsubMessage.MessageId is the ID of this message. It is guaranteed to be unique within the topic. PubsubMessage.PublishTime is the time at which the message was published. Notifications are only sent if the topic is non-empty. Topic names must be scoped to a project. Cloud Healthcare API service account must have publisher permissions on the given Pub/Sub topic. Not having adequate permissions causes the calls that send notifications to fail. If a notification can't be published to Pub/Sub, errors are logged to Cloud Logging (see Viewing error logs in Cloud Logging). If the number of errors exceeds a certain rate, some aren't submitted. Note that not all operations trigger notifications, see Configuring Pub/Sub notifications for specific details.
    sendForBulkImport Boolean
    Indicates whether or not to send Pub/Sub notifications on bulk import. Only supported for DICOM imports.

    NotificationConfigResponse, NotificationConfigResponseArgs

    PubsubTopic string
    The Pub/Sub topic that notifications of changes are published on. Supplied by the client. PubsubMessage.Data contains the resource name. PubsubMessage.MessageId is the ID of this message. It is guaranteed to be unique within the topic. PubsubMessage.PublishTime is the time at which the message was published. Notifications are only sent if the topic is non-empty. Topic names must be scoped to a project. Cloud Healthcare API service account must have publisher permissions on the given Pub/Sub topic. Not having adequate permissions causes the calls that send notifications to fail. If a notification can't be published to Pub/Sub, errors are logged to Cloud Logging (see Viewing error logs in Cloud Logging). If the number of errors exceeds a certain rate, some aren't submitted. Note that not all operations trigger notifications, see Configuring Pub/Sub notifications for specific details.
    SendForBulkImport bool
    Indicates whether or not to send Pub/Sub notifications on bulk import. Only supported for DICOM imports.
    PubsubTopic string
    The Pub/Sub topic that notifications of changes are published on. Supplied by the client. PubsubMessage.Data contains the resource name. PubsubMessage.MessageId is the ID of this message. It is guaranteed to be unique within the topic. PubsubMessage.PublishTime is the time at which the message was published. Notifications are only sent if the topic is non-empty. Topic names must be scoped to a project. Cloud Healthcare API service account must have publisher permissions on the given Pub/Sub topic. Not having adequate permissions causes the calls that send notifications to fail. If a notification can't be published to Pub/Sub, errors are logged to Cloud Logging (see Viewing error logs in Cloud Logging). If the number of errors exceeds a certain rate, some aren't submitted. Note that not all operations trigger notifications, see Configuring Pub/Sub notifications for specific details.
    SendForBulkImport bool
    Indicates whether or not to send Pub/Sub notifications on bulk import. Only supported for DICOM imports.
    pubsubTopic String
    The Pub/Sub topic that notifications of changes are published on. Supplied by the client. PubsubMessage.Data contains the resource name. PubsubMessage.MessageId is the ID of this message. It is guaranteed to be unique within the topic. PubsubMessage.PublishTime is the time at which the message was published. Notifications are only sent if the topic is non-empty. Topic names must be scoped to a project. Cloud Healthcare API service account must have publisher permissions on the given Pub/Sub topic. Not having adequate permissions causes the calls that send notifications to fail. If a notification can't be published to Pub/Sub, errors are logged to Cloud Logging (see Viewing error logs in Cloud Logging). If the number of errors exceeds a certain rate, some aren't submitted. Note that not all operations trigger notifications, see Configuring Pub/Sub notifications for specific details.
    sendForBulkImport Boolean
    Indicates whether or not to send Pub/Sub notifications on bulk import. Only supported for DICOM imports.
    pubsubTopic string
    The Pub/Sub topic that notifications of changes are published on. Supplied by the client. PubsubMessage.Data contains the resource name. PubsubMessage.MessageId is the ID of this message. It is guaranteed to be unique within the topic. PubsubMessage.PublishTime is the time at which the message was published. Notifications are only sent if the topic is non-empty. Topic names must be scoped to a project. Cloud Healthcare API service account must have publisher permissions on the given Pub/Sub topic. Not having adequate permissions causes the calls that send notifications to fail. If a notification can't be published to Pub/Sub, errors are logged to Cloud Logging (see Viewing error logs in Cloud Logging). If the number of errors exceeds a certain rate, some aren't submitted. Note that not all operations trigger notifications, see Configuring Pub/Sub notifications for specific details.
    sendForBulkImport boolean
    Indicates whether or not to send Pub/Sub notifications on bulk import. Only supported for DICOM imports.
    pubsub_topic str
    The Pub/Sub topic that notifications of changes are published on. Supplied by the client. PubsubMessage.Data contains the resource name. PubsubMessage.MessageId is the ID of this message. It is guaranteed to be unique within the topic. PubsubMessage.PublishTime is the time at which the message was published. Notifications are only sent if the topic is non-empty. Topic names must be scoped to a project. Cloud Healthcare API service account must have publisher permissions on the given Pub/Sub topic. Not having adequate permissions causes the calls that send notifications to fail. If a notification can't be published to Pub/Sub, errors are logged to Cloud Logging (see Viewing error logs in Cloud Logging). If the number of errors exceeds a certain rate, some aren't submitted. Note that not all operations trigger notifications, see Configuring Pub/Sub notifications for specific details.
    send_for_bulk_import bool
    Indicates whether or not to send Pub/Sub notifications on bulk import. Only supported for DICOM imports.
    pubsubTopic String
    The Pub/Sub topic that notifications of changes are published on. Supplied by the client. PubsubMessage.Data contains the resource name. PubsubMessage.MessageId is the ID of this message. It is guaranteed to be unique within the topic. PubsubMessage.PublishTime is the time at which the message was published. Notifications are only sent if the topic is non-empty. Topic names must be scoped to a project. Cloud Healthcare API service account must have publisher permissions on the given Pub/Sub topic. Not having adequate permissions causes the calls that send notifications to fail. If a notification can't be published to Pub/Sub, errors are logged to Cloud Logging (see Viewing error logs in Cloud Logging). If the number of errors exceeds a certain rate, some aren't submitted. Note that not all operations trigger notifications, see Configuring Pub/Sub notifications for specific details.
    sendForBulkImport Boolean
    Indicates whether or not to send Pub/Sub notifications on bulk import. Only supported for DICOM imports.

    Package Details

    Repository
    Google Cloud Native pulumi/pulumi-google-native
    License
    Apache-2.0
    google-native logo

    Google Cloud Native is in preview. Google Cloud Classic is fully supported.

    Google Cloud Native v0.32.0 published on Wednesday, Nov 29, 2023 by Pulumi
    pulumi/pulumi-google-native