Google Cloud Native is in preview. Google Cloud Classic is fully supported.
google-native.translate/v3.Glossary
Explore with Pulumi AI
Google Cloud Native is in preview. Google Cloud Classic is fully supported.
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,
display_name: Optional[str] = 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/v3: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 glossaryResource = new GoogleNative.Translate.V3.Glossary("glossaryResource", new()
{
InputConfig = new GoogleNative.Translate.V3.Inputs.GlossaryInputConfigArgs
{
GcsSource = new GoogleNative.Translate.V3.Inputs.GcsSourceArgs
{
InputUri = "string",
},
},
DisplayName = "string",
LanguageCodesSet = new GoogleNative.Translate.V3.Inputs.LanguageCodesSetArgs
{
LanguageCodes = new[]
{
"string",
},
},
LanguagePair = new GoogleNative.Translate.V3.Inputs.LanguageCodePairArgs
{
SourceLanguageCode = "string",
TargetLanguageCode = "string",
},
Location = "string",
Name = "string",
Project = "string",
});
example, err := translate.NewGlossary(ctx, "glossaryResource", &translate.GlossaryArgs{
InputConfig: &translate.GlossaryInputConfigArgs{
GcsSource: &translate.GcsSourceArgs{
InputUri: pulumi.String("string"),
},
},
DisplayName: 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 glossaryResource = new Glossary("glossaryResource", GlossaryArgs.builder()
.inputConfig(GlossaryInputConfigArgs.builder()
.gcsSource(GcsSourceArgs.builder()
.inputUri("string")
.build())
.build())
.displayName("string")
.languageCodesSet(LanguageCodesSetArgs.builder()
.languageCodes("string")
.build())
.languagePair(LanguageCodePairArgs.builder()
.sourceLanguageCode("string")
.targetLanguageCode("string")
.build())
.location("string")
.name("string")
.project("string")
.build());
glossary_resource = google_native.translate.v3.Glossary("glossaryResource",
input_config={
"gcs_source": {
"input_uri": "string",
},
},
display_name="string",
language_codes_set={
"language_codes": ["string"],
},
language_pair={
"source_language_code": "string",
"target_language_code": "string",
},
location="string",
name="string",
project="string")
const glossaryResource = new google_native.translate.v3.Glossary("glossaryResource", {
inputConfig: {
gcsSource: {
inputUri: "string",
},
},
displayName: "string",
languageCodesSet: {
languageCodes: ["string"],
},
languagePair: {
sourceLanguageCode: "string",
targetLanguageCode: "string",
},
location: "string",
name: "string",
project: "string",
});
type: google-native:translate/v3:Glossary
properties:
displayName: string
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
In Python, inputs that are objects can be passed either as argument classes or as dictionary literals.
The Glossary resource accepts the following input properties:
- Input
Config Pulumi.Google Native. Translate. V3. Inputs. Glossary Input Config - Provides examples to build the glossary from. Total glossary must not exceed 10M Unicode codepoints.
- Display
Name string - Optional. The display name of the glossary.
- Language
Codes Pulumi.Set Google Native. Translate. V3. Inputs. Language Codes Set - Used with equivalent term set glossaries.
- Language
Pair Pulumi.Google Native. Translate. V3. Inputs. Language Code Pair - 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 GlossaryInput Config Args - Provides examples to build the glossary from. Total glossary must not exceed 10M Unicode codepoints.
- Display
Name string - Optional. The display name of the glossary.
- Language
Codes LanguageSet Codes Set Args - Used with equivalent term set glossaries.
- Language
Pair LanguageCode Pair Args - 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 GlossaryInput Config - Provides examples to build the glossary from. Total glossary must not exceed 10M Unicode codepoints.
- display
Name String - Optional. The display name of the glossary.
- language
Codes LanguageSet Codes Set - Used with equivalent term set glossaries.
- language
Pair LanguageCode Pair - 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 GlossaryInput Config - Provides examples to build the glossary from. Total glossary must not exceed 10M Unicode codepoints.
- display
Name string - Optional. The display name of the glossary.
- language
Codes LanguageSet Codes Set - Used with equivalent term set glossaries.
- language
Pair LanguageCode Pair - 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 GlossaryInput Config Args - Provides examples to build the glossary from. Total glossary must not exceed 10M Unicode codepoints.
- display_
name str - Optional. The display name of the glossary.
- language_
codes_ Languageset Codes Set Args - Used with equivalent term set glossaries.
- language_
pair LanguageCode Pair Args - 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
- input
Config Property Map - Provides examples to build the glossary from. Total glossary must not exceed 10M Unicode codepoints.
- display
Name String - Optional. The display name of the glossary.
- language
Codes Property MapSet - Used with equivalent term set glossaries.
- language
Pair 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:
- End
Time string - When the glossary creation was finished.
- Entry
Count int - The number of entries defined in the glossary.
- Id string
- The provider-assigned unique ID for this managed resource.
- Submit
Time string - When CreateGlossary was called.
- End
Time string - When the glossary creation was finished.
- Entry
Count int - The number of entries defined in the glossary.
- Id string
- The provider-assigned unique ID for this managed resource.
- Submit
Time string - When CreateGlossary was called.
- end
Time String - When the glossary creation was finished.
- entry
Count Integer - The number of entries defined in the glossary.
- id String
- The provider-assigned unique ID for this managed resource.
- submit
Time String - When CreateGlossary was called.
- end
Time string - When the glossary creation was finished.
- entry
Count number - The number of entries defined in the glossary.
- id string
- The provider-assigned unique ID for this managed resource.
- submit
Time 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.
- end
Time String - When the glossary creation was finished.
- entry
Count Number - The number of entries defined in the glossary.
- id String
- The provider-assigned unique ID for this managed resource.
- submit
Time String - When CreateGlossary was called.
Supporting Types
GcsSource, GcsSourceArgs
- Input
Uri string - Source data URI. For example,
gs://my_bucket/my_object
.
- Input
Uri string - Source data URI. For example,
gs://my_bucket/my_object
.
- input
Uri String - Source data URI. For example,
gs://my_bucket/my_object
.
- input
Uri string - Source data URI. For example,
gs://my_bucket/my_object
.
- input_
uri str - Source data URI. For example,
gs://my_bucket/my_object
.
- input
Uri String - Source data URI. For example,
gs://my_bucket/my_object
.
GcsSourceResponse, GcsSourceResponseArgs
- Input
Uri string - Source data URI. For example,
gs://my_bucket/my_object
.
- Input
Uri string - Source data URI. For example,
gs://my_bucket/my_object
.
- input
Uri String - Source data URI. For example,
gs://my_bucket/my_object
.
- input
Uri string - Source data URI. For example,
gs://my_bucket/my_object
.
- input_
uri str - Source data URI. For example,
gs://my_bucket/my_object
.
- input
Uri String - Source data URI. For example,
gs://my_bucket/my_object
.
GlossaryInputConfig, GlossaryInputConfigArgs
- Gcs
Source Pulumi.Google Native. Translate. V3. Inputs. Gcs Source - 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
): Two column file, tab- or comma-separated. The first column is source text. The second column is target text. No headers in this file. The first row contains data and 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
): Two column file, tab- or comma-separated. The first column is source text. The second column is target text. No headers in this file. The first row contains data and 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
): Two column file, tab- or comma-separated. The first column is source text. The second column is target text. No headers in this file. The first row contains data and 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
): Two column file, tab- or comma-separated. The first column is source text. The second column is target text. No headers in this file. The first row contains data and 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
): Two column file, tab- or comma-separated. The first column is source text. The second column is target text. No headers in this file. The first row contains data and 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 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
): Two column file, tab- or comma-separated. The first column is source text. The second column is target text. No headers in this file. The first row contains data and 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
- Gcs
Source Pulumi.Google Native. Translate. V3. Inputs. Gcs Source Response - 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
): Two column file, tab- or comma-separated. The first column is source text. The second column is target text. No headers in this file. The first row contains data and 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 Response - 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
): Two column file, tab- or comma-separated. The first column is source text. The second column is target text. No headers in this file. The first row contains data and 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 Response - 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
): Two column file, tab- or comma-separated. The first column is source text. The second column is target text. No headers in this file. The first row contains data and 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 Response - 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
): Two column file, tab- or comma-separated. The first column is source text. The second column is target text. No headers in this file. The first row contains data and 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 Response - 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
): Two column file, tab- or comma-separated. The first column is source text. The second column is target text. No headers in this file. The first row contains data and 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 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
): Two column file, tab- or comma-separated. The first column is source text. The second column is target text. No headers in this file. The first row contains data and 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
- Source
Language stringCode - The ISO-639 language code of the input text, for example, "en-US". Expected to be an exact match for GlossaryTerm.language_code.
- Target
Language stringCode - The ISO-639 language code for translation output, for example, "zh-CN". Expected to be an exact match for GlossaryTerm.language_code.
- Source
Language stringCode - The ISO-639 language code of the input text, for example, "en-US". Expected to be an exact match for GlossaryTerm.language_code.
- Target
Language stringCode - The ISO-639 language code for translation output, for example, "zh-CN". Expected to be an exact match for GlossaryTerm.language_code.
- source
Language StringCode - The ISO-639 language code of the input text, for example, "en-US". Expected to be an exact match for GlossaryTerm.language_code.
- target
Language StringCode - The ISO-639 language code for translation output, for example, "zh-CN". Expected to be an exact match for GlossaryTerm.language_code.
- source
Language stringCode - The ISO-639 language code of the input text, for example, "en-US". Expected to be an exact match for GlossaryTerm.language_code.
- target
Language stringCode - The ISO-639 language code for translation output, for example, "zh-CN". Expected to be an exact match for GlossaryTerm.language_code.
- source_
language_ strcode - The ISO-639 language code of the input text, for example, "en-US". Expected to be an exact match for GlossaryTerm.language_code.
- target_
language_ strcode - The ISO-639 language code for translation output, for example, "zh-CN". Expected to be an exact match for GlossaryTerm.language_code.
- source
Language StringCode - The ISO-639 language code of the input text, for example, "en-US". Expected to be an exact match for GlossaryTerm.language_code.
- target
Language StringCode - The ISO-639 language code for translation output, for example, "zh-CN". Expected to be an exact match for GlossaryTerm.language_code.
LanguageCodePairResponse, LanguageCodePairResponseArgs
- Source
Language stringCode - The ISO-639 language code of the input text, for example, "en-US". Expected to be an exact match for GlossaryTerm.language_code.
- Target
Language stringCode - The ISO-639 language code for translation output, for example, "zh-CN". Expected to be an exact match for GlossaryTerm.language_code.
- Source
Language stringCode - The ISO-639 language code of the input text, for example, "en-US". Expected to be an exact match for GlossaryTerm.language_code.
- Target
Language stringCode - The ISO-639 language code for translation output, for example, "zh-CN". Expected to be an exact match for GlossaryTerm.language_code.
- source
Language StringCode - The ISO-639 language code of the input text, for example, "en-US". Expected to be an exact match for GlossaryTerm.language_code.
- target
Language StringCode - The ISO-639 language code for translation output, for example, "zh-CN". Expected to be an exact match for GlossaryTerm.language_code.
- source
Language stringCode - The ISO-639 language code of the input text, for example, "en-US". Expected to be an exact match for GlossaryTerm.language_code.
- target
Language stringCode - The ISO-639 language code for translation output, for example, "zh-CN". Expected to be an exact match for GlossaryTerm.language_code.
- source_
language_ strcode - The ISO-639 language code of the input text, for example, "en-US". Expected to be an exact match for GlossaryTerm.language_code.
- target_
language_ strcode - The ISO-639 language code for translation output, for example, "zh-CN". Expected to be an exact match for GlossaryTerm.language_code.
- source
Language StringCode - The ISO-639 language code of the input text, for example, "en-US". Expected to be an exact match for GlossaryTerm.language_code.
- target
Language StringCode - The ISO-639 language code for translation output, for example, "zh-CN". Expected to be an exact match for GlossaryTerm.language_code.
LanguageCodesSet, LanguageCodesSetArgs
- Language
Codes List<string> - The ISO-639 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 []string - The ISO-639 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 List<String> - The ISO-639 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 string[] - The ISO-639 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 ISO-639 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 List<String> - The ISO-639 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
- Language
Codes List<string> - The ISO-639 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 []string - The ISO-639 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 List<String> - The ISO-639 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 string[] - The ISO-639 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 ISO-639 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 List<String> - The ISO-639 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 Cloud Native is in preview. Google Cloud Classic is fully supported.