Docs Home Pulumi IaC Pulumi ESC Pulumi Cloud Packages Tutorials
  1. Packages
  2. Google Cloud Native
  3. API Docs
  4. translate
  5. translate/v3beta1
  6. Glossary

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.translate/v3beta1.Glossary

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 glossary and returns the long-running operation. Returns NOT_FOUND, if the project doesn’t exist.

    Create Glossary Resource

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

    Constructor syntax

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

@overload
def Glossary(resource_name: str,
             opts: Optional[ResourceOptions] = None,
             input_config: Optional[GlossaryInputConfigArgs] = None,
             language_codes_set: Optional[LanguageCodesSetArgs] = None,
             language_pair: Optional[LanguageCodePairArgs] = None,
             location: Optional[str] = None,
             name: Optional[str] = None,
             project: Optional[str] = None)
    func NewGlossary(ctx *Context, name string, args GlossaryArgs, opts ...ResourceOption) (*Glossary, error)
    public Glossary(string name, GlossaryArgs args, CustomResourceOptions? opts = null)
    public Glossary(String name, GlossaryArgs args)
public Glossary(String name, GlossaryArgs args, CustomResourceOptions options)

    type: google-native:translate/v3beta1:Glossary
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 GlossaryArgs
    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 GlossaryArgs
    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 GlossaryArgs
    The arguments to resource properties.
    opts ResourceOption
    Bag of options to control resource's behavior.
    name string
    The unique name of the resource.
    args GlossaryArgs
    The arguments to resource properties.
    opts CustomResourceOptions
    Bag of options to control resource's behavior.
    name String
    The unique name of the resource.
    args GlossaryArgs
    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 google_nativeGlossaryResource = new GoogleNative.Translate.V3Beta1.Glossary("google-nativeGlossaryResource", new()
{
    InputConfig = new GoogleNative.Translate.V3Beta1.Inputs.GlossaryInputConfigArgs
    {
        GcsSource = new GoogleNative.Translate.V3Beta1.Inputs.GcsSourceArgs
        {
            InputUri = "string",
        },
    },
    LanguageCodesSet = new GoogleNative.Translate.V3Beta1.Inputs.LanguageCodesSetArgs
    {
        LanguageCodes = new[]
        {
            "string",
        },
    },
    LanguagePair = new GoogleNative.Translate.V3Beta1.Inputs.LanguageCodePairArgs
    {
        SourceLanguageCode = "string",
        TargetLanguageCode = "string",
    },
    Location = "string",
    Name = "string",
    Project = "string",
});

    example, err := translatev3beta1.NewGlossary(ctx, "google-nativeGlossaryResource", &translatev3beta1.GlossaryArgs{
	InputConfig: &translate.GlossaryInputConfigArgs{
		GcsSource: &translate.GcsSourceArgs{
			InputUri: pulumi.String("string"),
		},
	},
	LanguageCodesSet: &translate.LanguageCodesSetArgs{
		LanguageCodes: pulumi.StringArray{
			pulumi.String("string"),
		},
	},
	LanguagePair: &translate.LanguageCodePairArgs{
		SourceLanguageCode: pulumi.String("string"),
		TargetLanguageCode: pulumi.String("string"),
	},
	Location: pulumi.String("string"),
	Name:     pulumi.String("string"),
	Project:  pulumi.String("string"),
})

    var google_nativeGlossaryResource = new Glossary("google-nativeGlossaryResource", GlossaryArgs.builder()
    .inputConfig(GlossaryInputConfigArgs.builder()
        .gcsSource(GcsSourceArgs.builder()
            .inputUri("string")
            .build())
        .build())
    .languageCodesSet(LanguageCodesSetArgs.builder()
        .languageCodes("string")
        .build())
    .languagePair(LanguageCodePairArgs.builder()
        .sourceLanguageCode("string")
        .targetLanguageCode("string")
        .build())
    .location("string")
    .name("string")
    .project("string")
    .build());

    google_native_glossary_resource = google_native.translate.v3beta1.Glossary("google-nativeGlossaryResource",
    input_config=google_native.translate.v3beta1.GlossaryInputConfigArgs(
        gcs_source=google_native.translate.v3beta1.GcsSourceArgs(
            input_uri="string",
        ),
    ),
    language_codes_set=google_native.translate.v3beta1.LanguageCodesSetArgs(
        language_codes=["string"],
    ),
    language_pair=google_native.translate.v3beta1.LanguageCodePairArgs(
        source_language_code="string",
        target_language_code="string",
    ),
    location="string",
    name="string",
    project="string")

    const google_nativeGlossaryResource = new google_native.translate.v3beta1.Glossary("google-nativeGlossaryResource", {
    inputConfig: {
        gcsSource: {
            inputUri: "string",
        },
    },
    languageCodesSet: {
        languageCodes: ["string"],
    },
    languagePair: {
        sourceLanguageCode: "string",
        targetLanguageCode: "string",
    },
    location: "string",
    name: "string",
    project: "string",
});

    type: google-native:translate/v3beta1:Glossary
properties:
    inputConfig:
        gcsSource:
            inputUri: string
    languageCodesSet:
        languageCodes:
            - string
    languagePair:
        sourceLanguageCode: string
        targetLanguageCode: string
    location: string
    name: string
    project: string

    Glossary 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 Glossary resource accepts the following input properties:

    InputConfig Pulumi.GoogleNative.Translate.V3Beta1.Inputs.GlossaryInputConfig
    Provides examples to build the glossary from. Total glossary must not exceed 10M Unicode codepoints.
    LanguageCodesSet Pulumi.GoogleNative.Translate.V3Beta1.Inputs.LanguageCodesSet
    Used with equivalent term set glossaries.
    LanguagePair Pulumi.GoogleNative.Translate.V3Beta1.Inputs.LanguageCodePair
    Used with unidirectional glossaries.
    Location string
    Name string
    The resource name of the glossary. Glossary names have the form projects/{project-number-or-id}/locations/{location-id}/glossaries/{glossary-id}.
    Project string
    InputConfig GlossaryInputConfigArgs
    Provides examples to build the glossary from. Total glossary must not exceed 10M Unicode codepoints.
    LanguageCodesSet LanguageCodesSetArgs
    Used with equivalent term set glossaries.
    LanguagePair LanguageCodePairArgs
    Used with unidirectional glossaries.
    Location string
    Name string
    The resource name of the glossary. Glossary names have the form projects/{project-number-or-id}/locations/{location-id}/glossaries/{glossary-id}.
    Project string
    inputConfig GlossaryInputConfig
    Provides examples to build the glossary from. Total glossary must not exceed 10M Unicode codepoints.
    languageCodesSet LanguageCodesSet
    Used with equivalent term set glossaries.
    languagePair LanguageCodePair
    Used with unidirectional glossaries.
    location String
    name String
    The resource name of the glossary. Glossary names have the form projects/{project-number-or-id}/locations/{location-id}/glossaries/{glossary-id}.
    project String
    inputConfig GlossaryInputConfig
    Provides examples to build the glossary from. Total glossary must not exceed 10M Unicode codepoints.
    languageCodesSet LanguageCodesSet
    Used with equivalent term set glossaries.
    languagePair LanguageCodePair
    Used with unidirectional glossaries.
    location string
    name string
    The resource name of the glossary. Glossary names have the form projects/{project-number-or-id}/locations/{location-id}/glossaries/{glossary-id}.
    project string
    input_config GlossaryInputConfigArgs
    Provides examples to build the glossary from. Total glossary must not exceed 10M Unicode codepoints.
    language_codes_set LanguageCodesSetArgs
    Used with equivalent term set glossaries.
    language_pair LanguageCodePairArgs
    Used with unidirectional glossaries.
    location str
    name str
    The resource name of the glossary. Glossary names have the form projects/{project-number-or-id}/locations/{location-id}/glossaries/{glossary-id}.
    project str
    inputConfig Property Map
    Provides examples to build the glossary from. Total glossary must not exceed 10M Unicode codepoints.
    languageCodesSet Property Map
    Used with equivalent term set glossaries.
    languagePair Property Map
    Used with unidirectional glossaries.
    location String
    name String
    The resource name of the glossary. Glossary names have the form projects/{project-number-or-id}/locations/{location-id}/glossaries/{glossary-id}.
    project String

    Outputs

    All input properties are implicitly available as output properties. Additionally, the Glossary resource produces the following output properties:

    EndTime string
    When the glossary creation was finished.
    EntryCount int
    The number of entries defined in the glossary.
    Id string
    The provider-assigned unique ID for this managed resource.
    SubmitTime string
    When CreateGlossary was called.
    EndTime string
    When the glossary creation was finished.
    EntryCount int
    The number of entries defined in the glossary.
    Id string
    The provider-assigned unique ID for this managed resource.
    SubmitTime string
    When CreateGlossary was called.
    endTime String
    When the glossary creation was finished.
    entryCount Integer
    The number of entries defined in the glossary.
    id String
    The provider-assigned unique ID for this managed resource.
    submitTime String
    When CreateGlossary was called.
    endTime string
    When the glossary creation was finished.
    entryCount number
    The number of entries defined in the glossary.
    id string
    The provider-assigned unique ID for this managed resource.
    submitTime string
    When CreateGlossary was called.
    end_time str
    When the glossary creation was finished.
    entry_count int
    The number of entries defined in the glossary.
    id str
    The provider-assigned unique ID for this managed resource.
    submit_time str
    When CreateGlossary was called.
    endTime String
    When the glossary creation was finished.
    entryCount Number
    The number of entries defined in the glossary.
    id String
    The provider-assigned unique ID for this managed resource.
    submitTime String
    When CreateGlossary was called.

    Supporting Types

    GcsSource, GcsSourceArgs

    InputUri string
    Source data URI. For example, gs://my_bucket/my_object.
    InputUri string
    Source data URI. For example, gs://my_bucket/my_object.
    inputUri String
    Source data URI. For example, gs://my_bucket/my_object.
    inputUri string
    Source data URI. For example, gs://my_bucket/my_object.
    input_uri str
    Source data URI. For example, gs://my_bucket/my_object.
    inputUri String
    Source data URI. For example, gs://my_bucket/my_object.

    GcsSourceResponse, GcsSourceResponseArgs

    InputUri string
    Source data URI. For example, gs://my_bucket/my_object.
    InputUri string
    Source data URI. For example, gs://my_bucket/my_object.
    inputUri String
    Source data URI. For example, gs://my_bucket/my_object.
    inputUri string
    Source data URI. For example, gs://my_bucket/my_object.
    input_uri str
    Source data URI. For example, gs://my_bucket/my_object.
    inputUri String
    Source data URI. For example, gs://my_bucket/my_object.

    GlossaryInputConfig, GlossaryInputConfigArgs

    GcsSource Pulumi.GoogleNative.Translate.V3Beta1.Inputs.GcsSource
    Google Cloud Storage location of glossary data. File format is determined based on the filename extension. API returns [google.rpc.Code.INVALID_ARGUMENT] for unsupported URI-s and file formats. Wildcards are not allowed. This must be a single file in one of the following formats: For unidirectional glossaries: - TSV/CSV (.tsv/.csv): 2 column file, tab- or comma-separated. The first column is source text. The second column is target text. The file must not contain headers. That is, the first row is data, not column names. - TMX (.tmx): TMX file with parallel data defining source/target term pairs. For equivalent term sets glossaries: - CSV (.csv): Multi-column CSV file defining equivalent glossary terms in multiple languages. See documentation for more information - glossaries.
    GcsSource GcsSource
    Google Cloud Storage location of glossary data. File format is determined based on the filename extension. API returns [google.rpc.Code.INVALID_ARGUMENT] for unsupported URI-s and file formats. Wildcards are not allowed. This must be a single file in one of the following formats: For unidirectional glossaries: - TSV/CSV (.tsv/.csv): 2 column file, tab- or comma-separated. The first column is source text. The second column is target text. The file must not contain headers. That is, the first row is data, not column names. - TMX (.tmx): TMX file with parallel data defining source/target term pairs. For equivalent term sets glossaries: - CSV (.csv): Multi-column CSV file defining equivalent glossary terms in multiple languages. See documentation for more information - glossaries.
    gcsSource GcsSource
    Google Cloud Storage location of glossary data. File format is determined based on the filename extension. API returns [google.rpc.Code.INVALID_ARGUMENT] for unsupported URI-s and file formats. Wildcards are not allowed. This must be a single file in one of the following formats: For unidirectional glossaries: - TSV/CSV (.tsv/.csv): 2 column file, tab- or comma-separated. The first column is source text. The second column is target text. The file must not contain headers. That is, the first row is data, not column names. - TMX (.tmx): TMX file with parallel data defining source/target term pairs. For equivalent term sets glossaries: - CSV (.csv): Multi-column CSV file defining equivalent glossary terms in multiple languages. See documentation for more information - glossaries.
    gcsSource GcsSource
    Google Cloud Storage location of glossary data. File format is determined based on the filename extension. API returns [google.rpc.Code.INVALID_ARGUMENT] for unsupported URI-s and file formats. Wildcards are not allowed. This must be a single file in one of the following formats: For unidirectional glossaries: - TSV/CSV (.tsv/.csv): 2 column file, tab- or comma-separated. The first column is source text. The second column is target text. The file must not contain headers. That is, the first row is data, not column names. - TMX (.tmx): TMX file with parallel data defining source/target term pairs. For equivalent term sets glossaries: - CSV (.csv): Multi-column CSV file defining equivalent glossary terms in multiple languages. See documentation for more information - glossaries.
    gcs_source GcsSource
    Google Cloud Storage location of glossary data. File format is determined based on the filename extension. API returns [google.rpc.Code.INVALID_ARGUMENT] for unsupported URI-s and file formats. Wildcards are not allowed. This must be a single file in one of the following formats: For unidirectional glossaries: - TSV/CSV (.tsv/.csv): 2 column file, tab- or comma-separated. The first column is source text. The second column is target text. The file must not contain headers. That is, the first row is data, not column names. - TMX (.tmx): TMX file with parallel data defining source/target term pairs. For equivalent term sets glossaries: - CSV (.csv): Multi-column CSV file defining equivalent glossary terms in multiple languages. See documentation for more information - glossaries.
    gcsSource Property Map
    Google Cloud Storage location of glossary data. File format is determined based on the filename extension. API returns [google.rpc.Code.INVALID_ARGUMENT] for unsupported URI-s and file formats. Wildcards are not allowed. This must be a single file in one of the following formats: For unidirectional glossaries: - TSV/CSV (.tsv/.csv): 2 column file, tab- or comma-separated. The first column is source text. The second column is target text. The file must not contain headers. That is, the first row is data, not column names. - TMX (.tmx): TMX file with parallel data defining source/target term pairs. For equivalent term sets glossaries: - CSV (.csv): Multi-column CSV file defining equivalent glossary terms in multiple languages. See documentation for more information - glossaries.

    GlossaryInputConfigResponse, GlossaryInputConfigResponseArgs

    GcsSource Pulumi.GoogleNative.Translate.V3Beta1.Inputs.GcsSourceResponse
    Google Cloud Storage location of glossary data. File format is determined based on the filename extension. API returns [google.rpc.Code.INVALID_ARGUMENT] for unsupported URI-s and file formats. Wildcards are not allowed. This must be a single file in one of the following formats: For unidirectional glossaries: - TSV/CSV (.tsv/.csv): 2 column file, tab- or comma-separated. The first column is source text. The second column is target text. The file must not contain headers. That is, the first row is data, not column names. - TMX (.tmx): TMX file with parallel data defining source/target term pairs. For equivalent term sets glossaries: - CSV (.csv): Multi-column CSV file defining equivalent glossary terms in multiple languages. See documentation for more information - glossaries.
    GcsSource GcsSourceResponse
    Google Cloud Storage location of glossary data. File format is determined based on the filename extension. API returns [google.rpc.Code.INVALID_ARGUMENT] for unsupported URI-s and file formats. Wildcards are not allowed. This must be a single file in one of the following formats: For unidirectional glossaries: - TSV/CSV (.tsv/.csv): 2 column file, tab- or comma-separated. The first column is source text. The second column is target text. The file must not contain headers. That is, the first row is data, not column names. - TMX (.tmx): TMX file with parallel data defining source/target term pairs. For equivalent term sets glossaries: - CSV (.csv): Multi-column CSV file defining equivalent glossary terms in multiple languages. See documentation for more information - glossaries.
    gcsSource GcsSourceResponse
    Google Cloud Storage location of glossary data. File format is determined based on the filename extension. API returns [google.rpc.Code.INVALID_ARGUMENT] for unsupported URI-s and file formats. Wildcards are not allowed. This must be a single file in one of the following formats: For unidirectional glossaries: - TSV/CSV (.tsv/.csv): 2 column file, tab- or comma-separated. The first column is source text. The second column is target text. The file must not contain headers. That is, the first row is data, not column names. - TMX (.tmx): TMX file with parallel data defining source/target term pairs. For equivalent term sets glossaries: - CSV (.csv): Multi-column CSV file defining equivalent glossary terms in multiple languages. See documentation for more information - glossaries.
    gcsSource GcsSourceResponse
    Google Cloud Storage location of glossary data. File format is determined based on the filename extension. API returns [google.rpc.Code.INVALID_ARGUMENT] for unsupported URI-s and file formats. Wildcards are not allowed. This must be a single file in one of the following formats: For unidirectional glossaries: - TSV/CSV (.tsv/.csv): 2 column file, tab- or comma-separated. The first column is source text. The second column is target text. The file must not contain headers. That is, the first row is data, not column names. - TMX (.tmx): TMX file with parallel data defining source/target term pairs. For equivalent term sets glossaries: - CSV (.csv): Multi-column CSV file defining equivalent glossary terms in multiple languages. See documentation for more information - glossaries.
    gcs_source GcsSourceResponse
    Google Cloud Storage location of glossary data. File format is determined based on the filename extension. API returns [google.rpc.Code.INVALID_ARGUMENT] for unsupported URI-s and file formats. Wildcards are not allowed. This must be a single file in one of the following formats: For unidirectional glossaries: - TSV/CSV (.tsv/.csv): 2 column file, tab- or comma-separated. The first column is source text. The second column is target text. The file must not contain headers. That is, the first row is data, not column names. - TMX (.tmx): TMX file with parallel data defining source/target term pairs. For equivalent term sets glossaries: - CSV (.csv): Multi-column CSV file defining equivalent glossary terms in multiple languages. See documentation for more information - glossaries.
    gcsSource Property Map
    Google Cloud Storage location of glossary data. File format is determined based on the filename extension. API returns [google.rpc.Code.INVALID_ARGUMENT] for unsupported URI-s and file formats. Wildcards are not allowed. This must be a single file in one of the following formats: For unidirectional glossaries: - TSV/CSV (.tsv/.csv): 2 column file, tab- or comma-separated. The first column is source text. The second column is target text. The file must not contain headers. That is, the first row is data, not column names. - TMX (.tmx): TMX file with parallel data defining source/target term pairs. For equivalent term sets glossaries: - CSV (.csv): Multi-column CSV file defining equivalent glossary terms in multiple languages. See documentation for more information - glossaries.

    LanguageCodePair, LanguageCodePairArgs

    SourceLanguageCode string
    The BCP-47 language code of the input text, for example, "en-US". Expected to be an exact match for GlossaryTerm.language_code.
    TargetLanguageCode string
    The BCP-47 language code for translation output, for example, "zh-CN". Expected to be an exact match for GlossaryTerm.language_code.
    SourceLanguageCode string
    The BCP-47 language code of the input text, for example, "en-US". Expected to be an exact match for GlossaryTerm.language_code.
    TargetLanguageCode string
    The BCP-47 language code for translation output, for example, "zh-CN". Expected to be an exact match for GlossaryTerm.language_code.
    sourceLanguageCode String
    The BCP-47 language code of the input text, for example, "en-US". Expected to be an exact match for GlossaryTerm.language_code.
    targetLanguageCode String
    The BCP-47 language code for translation output, for example, "zh-CN". Expected to be an exact match for GlossaryTerm.language_code.
    sourceLanguageCode string
    The BCP-47 language code of the input text, for example, "en-US". Expected to be an exact match for GlossaryTerm.language_code.
    targetLanguageCode string
    The BCP-47 language code for translation output, for example, "zh-CN". Expected to be an exact match for GlossaryTerm.language_code.
    source_language_code str
    The BCP-47 language code of the input text, for example, "en-US". Expected to be an exact match for GlossaryTerm.language_code.
    target_language_code str
    The BCP-47 language code for translation output, for example, "zh-CN". Expected to be an exact match for GlossaryTerm.language_code.
    sourceLanguageCode String
    The BCP-47 language code of the input text, for example, "en-US". Expected to be an exact match for GlossaryTerm.language_code.
    targetLanguageCode String
    The BCP-47 language code for translation output, for example, "zh-CN". Expected to be an exact match for GlossaryTerm.language_code.

    LanguageCodePairResponse, LanguageCodePairResponseArgs

    SourceLanguageCode string
    The BCP-47 language code of the input text, for example, "en-US". Expected to be an exact match for GlossaryTerm.language_code.
    TargetLanguageCode string
    The BCP-47 language code for translation output, for example, "zh-CN". Expected to be an exact match for GlossaryTerm.language_code.
    SourceLanguageCode string
    The BCP-47 language code of the input text, for example, "en-US". Expected to be an exact match for GlossaryTerm.language_code.
    TargetLanguageCode string
    The BCP-47 language code for translation output, for example, "zh-CN". Expected to be an exact match for GlossaryTerm.language_code.
    sourceLanguageCode String
    The BCP-47 language code of the input text, for example, "en-US". Expected to be an exact match for GlossaryTerm.language_code.
    targetLanguageCode String
    The BCP-47 language code for translation output, for example, "zh-CN". Expected to be an exact match for GlossaryTerm.language_code.
    sourceLanguageCode string
    The BCP-47 language code of the input text, for example, "en-US". Expected to be an exact match for GlossaryTerm.language_code.
    targetLanguageCode string
    The BCP-47 language code for translation output, for example, "zh-CN". Expected to be an exact match for GlossaryTerm.language_code.
    source_language_code str
    The BCP-47 language code of the input text, for example, "en-US". Expected to be an exact match for GlossaryTerm.language_code.
    target_language_code str
    The BCP-47 language code for translation output, for example, "zh-CN". Expected to be an exact match for GlossaryTerm.language_code.
    sourceLanguageCode String
    The BCP-47 language code of the input text, for example, "en-US". Expected to be an exact match for GlossaryTerm.language_code.
    targetLanguageCode String
    The BCP-47 language code for translation output, for example, "zh-CN". Expected to be an exact match for GlossaryTerm.language_code.

    LanguageCodesSet, LanguageCodesSetArgs

    LanguageCodes List<string>
    The BCP-47 language code(s) for terms defined in the glossary. All entries are unique. The list contains at least two entries. Expected to be an exact match for GlossaryTerm.language_code.
    LanguageCodes []string
    The BCP-47 language code(s) for terms defined in the glossary. All entries are unique. The list contains at least two entries. Expected to be an exact match for GlossaryTerm.language_code.
    languageCodes List<String>
    The BCP-47 language code(s) for terms defined in the glossary. All entries are unique. The list contains at least two entries. Expected to be an exact match for GlossaryTerm.language_code.
    languageCodes string[]
    The BCP-47 language code(s) for terms defined in the glossary. All entries are unique. The list contains at least two entries. Expected to be an exact match for GlossaryTerm.language_code.
    language_codes Sequence[str]
    The BCP-47 language code(s) for terms defined in the glossary. All entries are unique. The list contains at least two entries. Expected to be an exact match for GlossaryTerm.language_code.
    languageCodes List<String>
    The BCP-47 language code(s) for terms defined in the glossary. All entries are unique. The list contains at least two entries. Expected to be an exact match for GlossaryTerm.language_code.

    LanguageCodesSetResponse, LanguageCodesSetResponseArgs

    LanguageCodes List<string>
    The BCP-47 language code(s) for terms defined in the glossary. All entries are unique. The list contains at least two entries. Expected to be an exact match for GlossaryTerm.language_code.
    LanguageCodes []string
    The BCP-47 language code(s) for terms defined in the glossary. All entries are unique. The list contains at least two entries. Expected to be an exact match for GlossaryTerm.language_code.
    languageCodes List<String>
    The BCP-47 language code(s) for terms defined in the glossary. All entries are unique. The list contains at least two entries. Expected to be an exact match for GlossaryTerm.language_code.
    languageCodes string[]
    The BCP-47 language code(s) for terms defined in the glossary. All entries are unique. The list contains at least two entries. Expected to be an exact match for GlossaryTerm.language_code.
    language_codes Sequence[str]
    The BCP-47 language code(s) for terms defined in the glossary. All entries are unique. The list contains at least two entries. Expected to be an exact match for GlossaryTerm.language_code.
    languageCodes List<String>
    The BCP-47 language code(s) for terms defined in the glossary. All entries are unique. The list contains at least two entries. Expected to be an exact match for GlossaryTerm.language_code.

    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