Expand description
Data structures used by operation inputs/outputs.
Modules§
- Builders
- Error types that Amazon Q Connect can respond with.
Structs§
Information about an agent.
A type that specifies the AI Agent ID configuration data when mapping an AI Agents to be used for an AI Agent type on a session or assistant.
The data for the AI Agent.
The summary of the AI Agent.
The summary of the AI Agent version.
Contains details about how to handle harmful content.
The policy configuration details for the AI Guardrail's contextual grounding policy.
The data for the AI Guardrail
Contains details about PII entities and regular expressions to configure for the AI Guardrail.
The summary of the AI Guardrail.
Contains details about topics that the AI Guardrail should identify and deny.
The summary of the AI Guardrail version.
Contains details about the word policy to configured for the AI Guardrail.
The data for the AI Prompt
The summary of the AI Prompt.
The summary of the AI Prompt version.
Content association data for a step-by-step guide.
The configuration for the
ANSWER_RECOMMENDATIONAI Agent type.Configuration information for Amazon AppIntegrations to automatically ingest content.
Information about the assistant association.
Summary information about the assistant association.
The capability configuration for an Amazon Q in Connect assistant.
The assistant data.
The configuration information for the Amazon Q in Connect assistant integration.
Summary information about the assistant.
The configuration for an Amazon Q in Connect Assistant Association.
Settings for a foundation model used to parse documents for a data source.
Details about how to chunk the documents in the data source. A chunk refers to an excerpt from a data source that is returned when the knowledge base that it belongs to is queried.
Contains information about where the text with a citation begins and ends in the generated output.
The configuration information of the Amazon Connect data source.
Information about the content association.
Summary information about a content association.
Information about the content.
Details about the content data.
Reference information about the content.
Summary information about the content.
The conversation context to include in SendMessage.
The conversation state associated to a message.
The customer profile attributes that are used with the message template.
Summary of the data.
The document.
The text of the document.
The email header to include in email messages.
The content of the message template that applies to the email channel subtype.
The body to use in email messages.
The extended data of a message template.
The configuration information of the external data source.
A search filter.
Configurations for when you choose fixed-size chunking. If you set the
chunkingStrategyasNONE, exclude this field.The feedback information for a generative target type.
Details about generative data.
Reference information about generative content.
The configuration information of the grouping of Amazon Q in Connect users.
Contains filter strengths for harmful content. AI Guardrail's support the following content filters to detect and filter harmful user inputs and FM-generated outputs.
-
Hate: Describes input prompts and model responses that discriminate, criticize, insult, denounce, or dehumanize a person or group on the basis of an identity (such as race, ethnicity, gender, religion, sexual orientation, ability, and national origin).
-
Insults: Describes input prompts and model responses that includes demeaning, humiliating, mocking, insulting, or belittling language. This type of language is also labeled as bullying.
-
Sexual: Describes input prompts and model responses that indicates sexual interest, activity, or arousal using direct or indirect references to body parts, physical traits, or sex.
-
Violence: Describes input prompts and model responses that includes glorification of, or threats to inflict physical pain, hurt, or injury toward a person, group, or thing.
Content filtering depends on the confidence classification of user inputs and FM responses across each of the four harmful categories. All input and output statements are classified into one of four confidence levels (NONE, LOW, MEDIUM, HIGH) for each harmful category. For example, if a statement is classified as Hate with HIGH confidence, the likelihood of the statement representing hateful content is high. A single statement can be classified across multiple categories with varying confidence levels. For example, a single statement can be classified as Hate with HIGH confidence, Insults with LOW confidence, Sexual with NONE confidence, and Violence with MEDIUM confidence.
-
The filter configuration details for the AI Guardrail's contextual grounding filter.
The managed word list to configure for the AI Guardrail.
The PII entity to configure for the AI Guardrail.
The regular expression to configure for the AI Guardrail.
Details about topics for the AI Guardrail to identify and deny.
A word to configure for the AI Guardrail.
Settings for hierarchical document chunking for a data source. Hierarchical chunking splits documents into layers of chunks where the first layer contains large chunks, and the second layer contains smaller chunks derived from the first layer.
Token settings for each layer.
Offset specification to describe highlighting of document excerpts for rendering search results and recommendations.
Summary information about the import job.
Summary information about the import job.
Details about the detected intent.
Information about the Amazon Q intent.
The data of the configuration for a
KNOWLEDGE_BASEtype Amazon Q in Connect Assistant Association.Association information about the knowledge base.
Information about the knowledge base.
Summary information about the knowledge base.
The configuration for the
MANUAL_SEARCHAI Agent type.The message input.
The message output.
Information about the message template attachment.
The attributes that are used with the message template.
The data of a message template.
The message template fields to filter the message template query results by. The following is the list of supported field names:
-
name
-
description
-
channel
-
channelSubtype
-
language
-
qualifier
-
createdTime
-
lastModifiedTime
-
lastModifiedBy
-
groupingConfiguration.criteria
-
groupingConfiguration.values
-
The message template fields to order the message template query results by. The following is the list of supported field names:
-
name
-
description
-
channel
-
channelSubtype
-
language
-
qualifier
-
createdTime
-
lastModifiedTime
-
lastModifiedBy
-
groupingConfiguration.criteria
-
groupingConfiguration.values
-
The message template fields to query message templates by. The following is the list of supported field names:
-
name
-
description
-
The search expression of the message template.
The result of message template search.
The summary of the message template.
The summary of the message template version.
An error occurred when creating a recommendation.
Settings for parsing document contents. By default, the service converts the contents of each document into text before splitting it into chunks. To improve processing of PDF files with tables and images, you can configure the data source to convert the pages of text into images and use a model to describe the contents of each page.
Instructions for interpreting the contents of a document.
The condition for the query.
Data associated with the QUERY RecommendationTriggerType.
Information about the text to search for.
The content of the quick response stored in different media types.
Information about the quick response.
The quick response fields to filter the quick response query results by.
The following is the list of supported field names.
-
name
-
description
-
shortcutKey
-
isActive
-
channels
-
language
-
contentType
-
createdTime
-
lastModifiedTime
-
lastModifiedBy
-
groupingConfiguration.criteria
-
groupingConfiguration.values
-
The quick response fields to order the quick response query results by.
The following is the list of supported field names.
-
name
-
description
-
shortcutKey
-
isActive
-
channels
-
language
-
contentType
-
createdTime
-
lastModifiedTime
-
lastModifiedBy
-
groupingConfiguration.criteria
-
groupingConfiguration.values
-
The quick response fields to query quick responses by.
The following is the list of supported field names.
-
content
-
name
-
description
-
shortcutKey
-
Information about the import job.
The result of quick response search.
The summary information about the quick response.
Details about the source content ranking data.
Information about the recommendation.
A recommendation trigger provides context on the event that produced the referenced recommendations. Recommendations are only referenced in
recommendationIdsby a single RecommendationTrigger.Information about how to render the content.
Information about the result.
The list of key-value pairs that are stored on the session.
The search expression.
A URL for crawling.
The configuration for AI Agents of type SELF_SERVICE.
The conversation history data to included in conversation context data before the the Amazon Q in Connect session..
Settings for semantic document chunking for a data source. Semantic chunking splits a document into smaller documents based on groups of similar content derived from the text with natural language processing.
The configuration information for the customer managed key used for encryption.
Information about the session.
The configuration information for the session integration.
Summary information about the session.
The content of the message template that applies to the SMS channel subtype.
The body to use in SMS messages.
Details about the source content data.
The system attributes that are used with the message template.
The system endpoint attributes that are used with the message template.
A leaf node condition which can be used to specify a tag condition.
Details about the source content text data.
The configuration for a prompt template that supports full textual prompt configuration using a YAML prompt.
The message data in text type.
The configuration of the URL/URLs for the web content that you want to crawl. You should be authorized to crawl the URLs.
Contains details about how to ingest the documents in a data source.
The configuration details for the web data source.
The configuration of crawl limits for the web URLs.
Enums§
- When writing a match expression against
AiAgentAssociationConfigurationType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. A typed union that specifies the configuration based on the type of AI Agent.
- When writing a match expression against
AiAgentType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
AiPromptApiFormat, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. A typed union that specifies the configuration for a prompt template based on its type.
- When writing a match expression against
AiPromptTemplateType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
AiPromptType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. The data that is input into Amazon Q in Connect as a result of the assistant association.
The data that is output as a result of the assistant association.
- When writing a match expression against
AssistantCapabilityType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
AssistantStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
AssistantType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. A typed union of the data of the configuration for an Amazon Q in Connect Assistant Association.
- When writing a match expression against
AssociationType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
ChannelSubtype, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
ChunkingStrategy, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. The configuration information of the external data source.
The contents of a content association.
- When writing a match expression against
ContentAssociationType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
ContentDisposition, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. Information about the feedback.
- When writing a match expression against
ContentStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
ConversationStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
ConversationStatusReason, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. Details about the data.
Reference data.
- When writing a match expression against
ExternalSource, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
FilterField, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
FilterOperator, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
GuardrailContentFilterType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
GuardrailContextualGroundingFilterType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
GuardrailFilterStrength, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
GuardrailManagedWordsType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
GuardrailPiiEntityType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
GuardrailSensitiveInformationAction, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
GuardrailTopicType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
ImportJobStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
ImportJobType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
KnowledgeBaseSearchType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
KnowledgeBaseStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
KnowledgeBaseType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. Source configuration for managed resources.
The message data.
- When writing a match expression against
MessageTemplateAttributeType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. The container of the message template body.
The container of message template content.
- When writing a match expression against
MessageTemplateFilterOperator, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
MessageTemplateQueryOperator, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
MessageType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. A list of conditions which would be applied together with an
ORcondition.- When writing a match expression against
Order, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
Origin, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
ParsingStrategy, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
Participant, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
Priority, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. Information about how to query content.
- When writing a match expression against
QueryConditionComparisonOperator, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
QueryConditionFieldName, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. Input information for the query.
- When writing a match expression against
QueryResultType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. The container quick response content.
The container of quick response data.
- When writing a match expression against
QuickResponseFilterOperator, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
QuickResponseQueryOperator, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
QuickResponseStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
RecommendationSourceType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. A union type containing information related to the trigger.
- When writing a match expression against
RecommendationTriggerType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
RecommendationType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
ReferenceType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
Relevance, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
RelevanceLevel, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. A union type that specifies the data stored on the session.
- When writing a match expression against
SessionDataNamespace, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. Configuration information about the external data source.
- When writing a match expression against
SourceContentType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
Status, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
SyncStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. An object that can be used to specify Tag conditions.
- When writing a match expression against
TargetType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
VisibilityStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
WebScopeType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.