Expand description
Data structures used by operation inputs/outputs.
Modules§
Structs§
- Event
Type Summary Returns information about an event that has triggered a notification rule.
- List
Event Types Filter Information about a filter to apply to the list of returned event types. You can filter by resource type or service name.
- List
Notification Rules Filter Information about a filter to apply to the list of returned notification rules. You can filter by event type, owner, resource, or target.
- List
Targets Filter Information about a filter to apply to the list of returned targets. You can filter by target type, address, or status. For example, to filter results to notification rules that have active Chatbot topics as targets, you could specify a ListTargetsFilter Name as
TargetType
and a Value ofSNS
, and a Name ofTARGET_STATUS
and a Value ofACTIVE
.- Notification
Rule Summary Information about a specified notification rule.
- Target
Information about the Chatbot topics or Chatbot clients associated with a notification rule.
- Target
Summary Information about the targets specified for a notification rule.
Enums§
- Detail
Type - When writing a match expression against
DetailType
, 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. - List
Event Types Filter Name - When writing a match expression against
ListEventTypesFilterName
, 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. - List
Notification Rules Filter Name - When writing a match expression against
ListNotificationRulesFilterName
, 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. - List
Targets Filter Name - When writing a match expression against
ListTargetsFilterName
, 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. - Notification
Rule Status - When writing a match expression against
NotificationRuleStatus
, 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. - Target
Status - When writing a match expression against
TargetStatus
, 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.