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
google-native.translate/v3.getGlossary
Explore with Pulumi AI
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
Gets a glossary. Returns NOT_FOUND, if the glossary doesn’t exist.
Using getGlossary
Two invocation forms are available. The direct form accepts plain arguments and either blocks until the result value is available, or returns a Promise-wrapped result. The output form accepts Input-wrapped arguments and returns an Output-wrapped result.
function getGlossary(args: GetGlossaryArgs, opts?: InvokeOptions): Promise<GetGlossaryResult>
function getGlossaryOutput(args: GetGlossaryOutputArgs, opts?: InvokeOptions): Output<GetGlossaryResult>
def get_glossary(glossary_id: Optional[str] = None,
location: Optional[str] = None,
project: Optional[str] = None,
opts: Optional[InvokeOptions] = None) -> GetGlossaryResult
def get_glossary_output(glossary_id: Optional[pulumi.Input[str]] = None,
location: Optional[pulumi.Input[str]] = None,
project: Optional[pulumi.Input[str]] = None,
opts: Optional[InvokeOptions] = None) -> Output[GetGlossaryResult]
func LookupGlossary(ctx *Context, args *LookupGlossaryArgs, opts ...InvokeOption) (*LookupGlossaryResult, error)
func LookupGlossaryOutput(ctx *Context, args *LookupGlossaryOutputArgs, opts ...InvokeOption) LookupGlossaryResultOutput
> Note: This function is named LookupGlossary
in the Go SDK.
public static class GetGlossary
{
public static Task<GetGlossaryResult> InvokeAsync(GetGlossaryArgs args, InvokeOptions? opts = null)
public static Output<GetGlossaryResult> Invoke(GetGlossaryInvokeArgs args, InvokeOptions? opts = null)
}
public static CompletableFuture<GetGlossaryResult> getGlossary(GetGlossaryArgs args, InvokeOptions options)
// Output-based functions aren't available in Java yet
fn::invoke:
function: google-native:translate/v3:getGlossary
arguments:
# arguments dictionary
The following arguments are supported:
- Glossary
Id string - Location string
- Project string
- Glossary
Id string - Location string
- Project string
- glossary
Id String - location String
- project String
- glossary
Id string - location string
- project string
- glossary_
id str - location str
- project str
- glossary
Id String - location String
- project String
getGlossary Result
The following output properties are available:
- Display
Name string - Optional. The display name of the glossary.
- End
Time string - When the glossary creation was finished.
- Entry
Count int - The number of entries defined in the glossary.
- Input
Config Pulumi.Google Native. Translate. V3. Outputs. Glossary Input Config Response - Provides examples to build the glossary from. Total glossary must not exceed 10M Unicode codepoints.
- Language
Codes Pulumi.Set Google Native. Translate. V3. Outputs. Language Codes Set Response - Used with equivalent term set glossaries.
- Language
Pair Pulumi.Google Native. Translate. V3. Outputs. Language Code Pair Response - Used with unidirectional glossaries.
- Name string
- The resource name of the glossary. Glossary names have the form
projects/{project-number-or-id}/locations/{location-id}/glossaries/{glossary-id}
. - Submit
Time string - When CreateGlossary was called.
- Display
Name string - Optional. The display name of the glossary.
- End
Time string - When the glossary creation was finished.
- Entry
Count int - The number of entries defined in the glossary.
- Input
Config GlossaryInput Config Response - Provides examples to build the glossary from. Total glossary must not exceed 10M Unicode codepoints.
- Language
Codes LanguageSet Codes Set Response - Used with equivalent term set glossaries.
- Language
Pair LanguageCode Pair Response - Used with unidirectional glossaries.
- Name string
- The resource name of the glossary. Glossary names have the form
projects/{project-number-or-id}/locations/{location-id}/glossaries/{glossary-id}
. - Submit
Time string - When CreateGlossary was called.
- display
Name String - Optional. The display name of the glossary.
- end
Time String - When the glossary creation was finished.
- entry
Count Integer - The number of entries defined in the glossary.
- input
Config GlossaryInput Config Response - Provides examples to build the glossary from. Total glossary must not exceed 10M Unicode codepoints.
- language
Codes LanguageSet Codes Set Response - Used with equivalent term set glossaries.
- language
Pair LanguageCode Pair Response - Used with unidirectional glossaries.
- name String
- The resource name of the glossary. Glossary names have the form
projects/{project-number-or-id}/locations/{location-id}/glossaries/{glossary-id}
. - submit
Time String - When CreateGlossary was called.
- display
Name string - Optional. The display name of the glossary.
- end
Time string - When the glossary creation was finished.
- entry
Count number - The number of entries defined in the glossary.
- input
Config GlossaryInput Config Response - Provides examples to build the glossary from. Total glossary must not exceed 10M Unicode codepoints.
- language
Codes LanguageSet Codes Set Response - Used with equivalent term set glossaries.
- language
Pair LanguageCode Pair Response - Used with unidirectional glossaries.
- name string
- The resource name of the glossary. Glossary names have the form
projects/{project-number-or-id}/locations/{location-id}/glossaries/{glossary-id}
. - submit
Time string - When CreateGlossary was called.
- display_
name str - Optional. The display name of the glossary.
- end_
time str - When the glossary creation was finished.
- entry_
count int - The number of entries defined in the glossary.
- input_
config GlossaryInput Config Response - Provides examples to build the glossary from. Total glossary must not exceed 10M Unicode codepoints.
- language_
codes_ Languageset Codes Set Response - Used with equivalent term set glossaries.
- language_
pair LanguageCode Pair Response - Used with unidirectional glossaries.
- name str
- The resource name of the glossary. Glossary names have the form
projects/{project-number-or-id}/locations/{location-id}/glossaries/{glossary-id}
. - submit_
time str - When CreateGlossary was called.
- display
Name String - Optional. The display name of the glossary.
- end
Time String - When the glossary creation was finished.
- entry
Count Number - The number of entries defined in the glossary.
- input
Config Property Map - Provides examples to build the glossary from. Total glossary must not exceed 10M Unicode codepoints.
- language
Codes Property MapSet - Used with equivalent term set glossaries.
- language
Pair Property Map - Used with unidirectional glossaries.
- name String
- The resource name of the glossary. Glossary names have the form
projects/{project-number-or-id}/locations/{location-id}/glossaries/{glossary-id}
. - submit
Time String - When CreateGlossary was called.
Supporting Types
GcsSourceResponse
- 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
.
GlossaryInputConfigResponse
- 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.
LanguageCodePairResponse
- 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.
LanguageCodesSetResponse
- 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.
Google Cloud Native v0.32.0 published on Wednesday, Nov 29, 2023 by Pulumi