Module aws_sdk_codestarnotifications::types

Data structures used by operation inputs/outputs.

Modules

• builders
  Builders
• error
  Error types that AWS CodeStar Notifications can respond with.

Structs

• EventTypeSummary

  Returns information about an event that has triggered a notification rule.

• ListEventTypesFilter

  Information about a filter to apply to the list of returned event types. You can filter by resource type or service name.

• ListNotificationRulesFilter

  Information about a filter to apply to the list of returned notification rules. You can filter by event type, owner, resource, or target.

• ListTargetsFilter

  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 of SNS, and a Name of TARGET_STATUS and a Value of ACTIVE.

• NotificationRuleSummary

  Information about a specified notification rule.

• Target

  Information about the Chatbot topics or Chatbot clients associated with a notification rule.

• TargetSummary

  Information about the targets specified for a notification rule.

Enums

• DetailType
  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.
• ListEventTypesFilterName
  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.
• ListNotificationRulesFilterName
  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.
• ListTargetsFilterName
  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.
• NotificationRuleStatus
  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.
• TargetStatus
  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.