Expand description
Data structures used by operation inputs/outputs.
Modules§
- Builders
- Error types that Amazon DataZone can respond with.
Structs§
Specifies the prediction (aka, the automatically generated piece of metadata) and the target (for example, a column name) that can be accepted.
Specifies the rule and the threshold under which a prediction can be accepted.
The accepted asset scope.
The details of the policy grant.
The grant filter for all domain units.
The all users grant filter.
The summary of the asset filter.
The listing of the asset in a data product.
A Amazon DataZone inventory asset.
The additional attributes of an inventory asset.
An asset published in an Amazon DataZone catalog.
The details of an asset published in an Amazon DataZone catalog.
The details of an asset published in an Amazon DataZone catalog.
Additional attributes of an inventory asset.
The revision of an inventory asset.
The asset scope.
The name map for assets.
The details of the asset type.
The asset type for the rule details.
The Amazon Athena properties of a connection.
The Amazon Athena properties of a connection.
The Amazon Athena properties patch of a connection.
The authentication configuration of a connection.
The authentication configuration of a connection.
The authentication configuration patch of a connection.
The authorization code properties of a connection.
The parameters of the console link specified as part of the environment action.
The location of a project.
The basic authentication credentials of a connection.
The configuration of the business name generation.
Part of the provisioning properties of the environment blueprint.
The column configuration of the asset filter.
The details of the parameters for the configurable environment action.
The configurable action of a Amazon DataZone environment.
The credentials of a connection.
The summary of a connection.
The details of the policy grant.
The details of the policy grant.
The details of the policy grant.
The details of the policy grant.
The details of the policy grant.
Specifies whether to create a project from project profile policy grant details.
The details of the policy grant.
The details of user parameters of an environment blueprint.
The data product.
The data product listing.
The asset of the data product listing.
The additional attributes of the asset of the data product.
The data product.
The data product revision.
The details of the error message that is returned if the operation cannot be successfully completed.
The activity details of the data source run.
The run lineage summary of a data source.
The details of a data source run.
The details of the data source.
The details of the last deployment of the environment.
The deployment properties of the Amazon DataZone blueprint.
Details of a glossary term attached to the inventory asset.
A summary of a Amazon DataZone domain.
The domain unit filter of the project grant filter.
The properties of a domain unit group.
The domain unit principal to whom the policy is granted.
The summary of the domain unit.
The target for the domain unit.
The properties of the domain unit user.
The details about the specified action configured for an environment. For example, the details of the specified console links for an analytics tool that is available in this environment.
The configuration details of an environment blueprint.
The details of an environment blueprint summary.
The configuration of an environment.
The environment configuration parameter.
The details of the environment configuration parameter.
The environment configuration user parameters.
The environment deployment details.
The failure reasons for the environment deployment.
The parameter details of an evironment profile.
The details of an environment profile.
The details of an environment.
Specifies whether the value is equal to an expression.
Specifies the error message that is returned if the operation cannot be successfully completed.
A search filter in Amazon DataZone.
A filter expression in Amazon DataZone.
The details of the form entry.
The details of the form entry.
The details of a metadata form.
The details of a metadata form.
The details of the metadata form type.
The details of a business glossary.
The details of a business glossary term.
The Amazon Web Services Glue connection.
The Amazon Web Services Glue connecton input.
The Amazon Web Services Glue connection patch.
The GlueOAuth2 credentials of a connection.
The Amazon Web Services Glue properties of a connection.
The properties of the Amazon Web Services Glue connection.
The Amazon Web Services Glue properties patch of a connection.
The configuration details of the Amazon Web Services Glue data source.
The configuration details of the Amazon Web Services Glue data source.
The details of the self granting status.
Specifies whether the value is greater than an expression.
Specifies whether the value is greater than or equal to an expression.
The details of a group in Amazon DataZone.
The details of a group profile.
The hyper pod properties of a Amazon Web Services Glue properties patch.
The hyper pod properties of a Amazon Web Services Glue properties patch.
The IAM properties of a connection.
The IAM properties of a connection.
The IAM properties patch of a connection.
The details of an IAM user profile in Amazon DataZone.
The details of the import of the metadata form type.
Specifies whether values are in the expression.
Specifies that the expression is not null.
Specifies that the expression is null.
The job run error.
The job run summary.
The Lake Formation configuration of the Data Lake blueprint.
Specifies that a value is less than an expression.
Specifies that a value is less than or equal to an expression.
Specifies that a value is like the expression.
The data lineage event summary.
The data lineage information.
The reference details for the data lineage node.
The summary of the data lineage node.
The details of a data lineage node type.
The data lineage run details.
The SQL query run details of a data lineage run.
The lineage sync schedule.
A revision of an asset published in a Amazon DataZone catalog.
A revision to be made to an asset published in a Amazon DataZone catalog.
The summary of the listing of the data product.
The results of the data product summary.
The enforcement details of a metadata form.
The reference of a metadata form.
The summary of the metadata form.
The metadata generation run.
The asset for which metadata was generated.
The name identifier.
Specifies that a value is not equal to the expression.
Specifies that a value is not in the expression.
Specifies that a value might be not like the expression.
The details of a notification generated in Amazon DataZone.
The details of the resource mentioned in a notification.
The OAuth2Client application.
The OAuth2 properties.
The open lineage run event summary.
The grant details of the override domain unit owners policy.
The details of the override project owners policy grant.
The properties of the domain unit owners group.
The properties of the domain unit owners group.
The properties of the owner user.
The properties of the owner user.
Physical connection requirements of a connection.
The physical endpoints of a connection.
A member of the policy grant list.
The configuration of the prediction.
Specifies the error message that is returned if the operation cannot be successfully completed.
The details of a project member.
The project policy grant principal.
The summary of a project profile.
The details of a Amazon DataZone project.
Specifies projects in which the rule is created.
The recommendation to be updated as part of the
UpdateDataSource
action.The details of the Amazon Redshift cluster storage.
The details of the credentials required to access an Amazon Redshift cluster.
The Amaon Redshift lineage sync configuration.
The Amaon Redshift lineage sync configuration.
The Amazon Redshift properties.
The Amazon Redshift properties.
Amazon Redshift properties patch.
The configuration details of the Amazon Redshift data source.
The configuration details of the Amazon Redshift data source.
The details for the self granting status for an Amazon Redshift data source.
The details of the Amazon Redshift Serverless workgroup storage.
The details of the automatically generated business metadata that is rejected.
Specifies the rule and the threshold under which a prediction can be rejected.
The relational filter configuration for the data source.
The details of a provisioned resource of this Amazon DataZone environment.
The row filter configuration details.
The scope of a rule.
The summary of the rule.
The asset statistics from the data source run.
The Amazon SageMaker run configuration.
The Amazon SageMaker run configuration.
The details of the schedule of the data source runs.
The details of the search.
The details of the way to sort search results.
The details for the self granting status.
The single sign-on details in Amazon DataZone.
The Spark EMR properties.
The Spark EMR properties.
The Spark EMR properties patch.
The Spark Amazon Web Services Glue args.
The Spark Amazon Web Services Glue properties.
The Spark Amazon Web Services Glue properties.
The single sign-on details of the user profile.
The details of the asset for which the subscription grant is created.
The details of the published asset for which the subscription grant is created.
The details of the published asset for which the subscription grant is created.
The published asset for which the subscription grant is to be created.
The data product listing.
The project that has the subscription grant.
The project that is to be given a subscription grant.
The details of the subscription grant.
The details of the subscription request.
The details of the subscription.
The details of the subscription target configuration.
The details of the subscription target.
The details of the term relations.
The time series data points form.
The time series data points form.
The summary of the time series data points form.
The topic of the notification.
The details of the policy of creating an environment.
The user details of a project member.
The details of the user profile.
The username and password of a connection.
Enums§
- When writing a match expression against
AcceptRuleBehavior
, 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 parameters of the environment action.
The configuration details of the asset filter.
- When writing a match expression against
AuthType
, 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
AuthenticationType
, 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 account ID of a project.
- When writing a match expression against
ChangeAction
, 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
ComputeEnvironments
, 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
ConfigurableActionTypeAuthorization
, 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 properties of a connection.
The properties of a connection.
The connection properties patch.
- When writing a match expression against
ConnectionStatus
, 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
ConnectionType
, 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
DataAssetActivityStatus
, 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
DataProductItemType
, 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
DataProductStatus
, 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 of the data source.
The configuration of the data source.
- When writing a match expression against
DataSourceErrorType
, 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
DataSourceRunStatus
, 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
DataSourceRunType
, 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
DataSourceStatus
, 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
DataZoneEntityType
, 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
DeploymentMode
, 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
DeploymentStatus
, 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
DeploymentType
, 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
DomainStatus
, 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
DomainUnitDesignation
, 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 grant filter for the domain unit. In the current release of Amazon DataZone, the only supported filter is the
allDomainUnitsGrantFilter
.The properties of the domain unit owner.
- When writing a match expression against
DomainVersion
, 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
EdgeDirection
, 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
EnableSetting
, 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
EntityType
, 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
EnvironmentStatus
, 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 event summary.
A search filter clause in Amazon DataZone.
- When writing a match expression against
FilterExpressionType
, 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
FilterStatus
, 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
FormTypeStatus
, 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
GlossaryStatus
, 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
GlossaryTermStatus
, 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
GlueConnectionType
, 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
GovernanceType
, 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 details of a listing for which a subscription is granted.
The details of a listing for which a subscription is to be granted.
The group principal to whom the policy is granted.
- When writing a match expression against
GroupProfileStatus
, 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
GroupSearchType
, 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
HyperPodOrchestrator
, 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
InventorySearchScope
, 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 details of a job run.
- When writing a match expression against
JobRunMode
, 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
JobRunStatus
, 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
JobType
, 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
LineageEventProcessingStatus
, 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
LineageImportStatus
, 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 details of a listing (aka asset published in a Amazon DataZone catalog).
- When writing a match expression against
ListingStatus
, 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
ManagedPolicyType
, 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 details about a project member.
The details about a project member.
- When writing a match expression against
MetadataGenerationRunStatus
, 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
MetadataGenerationRunType
, 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
MetadataGenerationTargetType
, 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 model of the API.
- When writing a match expression against
NotificationResourceType
, 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
NotificationRole
, 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
NotificationType
, 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
OAuth2GrantType
, 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
OpenLineageRunState
, 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
OverallDeploymentStatus
, 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 properties of a domain unit's owner.
The ID of the domain unit owners group.
The details of the policy grant.
The policy grant principal.
- When writing a match expression against
ProjectDesignation
, 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 project grant filter.
- When writing a match expression against
ProjectStatus
, 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
Protocol
, 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 provisioning configuration of the blueprint.
The provisioning properties of an environment blueprint.
Amazon Redshift credentials of a connection.
The details of the Amazon Redshift storage as part of the configuration of an Amazon Redshift data source run.
The Amazon Redshift storage properties.
The Amazon Web Services Region.
- When writing a match expression against
RejectRuleBehavior
, 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 row filter.
The row filter expression.
- When writing a match expression against
RuleAction
, 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 details of a rule.
- When writing a match expression against
RuleScopeSelectionMode
, 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 target of the rule.
- When writing a match expression against
RuleTargetType
, 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
RuleType
, 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 details of the search results.
- When writing a match expression against
SearchOutputAdditionalAttribute
, 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 details of the results of the
SearchListings
action.The details of the results of the
SearchTypes
action.- When writing a match expression against
SelfGrantStatus
, 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 details for the self granting status for a data source.
- When writing a match expression against
SortFieldConnection
, 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
SortFieldProject
, 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
SortKey
, 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
SortOrder
, 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. The published asset for which the subscription grant is created.
The principal that has the subscription grant for the asset.
The principal that is to be given a subscriptiong grant.
- When writing a match expression against
SubscriptionGrantOverallStatus
, 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
SubscriptionGrantStatus
, 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
SubscriptionRequestStatus
, 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
SubscriptionStatus
, 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
TargetEntityType
, 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
TaskStatus
, 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
TimeSeriesEntityType
, 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
Timezone
, 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
TypesSearchScope
, 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
UserAssignment
, 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
UserDesignation
, 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 user policy grant principal.
The details of the user profile in Amazon DataZone.
- When writing a match expression against
UserProfileStatus
, 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
UserProfileType
, 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
UserSearchType
, 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
UserType
, 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.