Copyright | (c) 2013-2021 Brendan Hay |
---|---|
License | Mozilla Public License, v. 2.0. |
Maintainer | Brendan Hay <brendan.g.hay+amazonka@gmail.com> |
Stability | auto-generated |
Portability | non-portable (GHC extensions) |
Safe Haskell | None |
Creates a rule. Creating rules is an administrator-level action. Any user who has permission to create rules will be able to access data processed by the rule.
Requires permission to access the CreateTopicRule action.
Synopsis
- data CreateTopicRule = CreateTopicRule' {}
- newCreateTopicRule :: Text -> TopicRulePayload -> CreateTopicRule
- createTopicRule_tags :: Lens' CreateTopicRule (Maybe Text)
- createTopicRule_ruleName :: Lens' CreateTopicRule Text
- createTopicRule_topicRulePayload :: Lens' CreateTopicRule TopicRulePayload
- data CreateTopicRuleResponse = CreateTopicRuleResponse' {
- newCreateTopicRuleResponse :: CreateTopicRuleResponse
Creating a Request
data CreateTopicRule Source #
The input for the CreateTopicRule operation.
See: newCreateTopicRule
smart constructor.
CreateTopicRule' | |
|
Instances
:: Text | |
-> TopicRulePayload | |
-> CreateTopicRule |
Create a value of CreateTopicRule
with all optional fields omitted.
Use generic-lens or optics to modify other optional fields.
The following record fields are available, with the corresponding lenses provided for backwards compatibility:
$sel:tags:CreateTopicRule'
, createTopicRule_tags
- Metadata which can be used to manage the topic rule.
For URI Request parameters use format: ...key1=value1&key2=value2...
For the CLI command-line parameter use format: --tags "key1=value1&key2=value2..."
For the cli-input-json file use format: "tags": "key1=value1&key2=value2..."
$sel:ruleName:CreateTopicRule'
, createTopicRule_ruleName
- The name of the rule.
$sel:topicRulePayload:CreateTopicRule'
, createTopicRule_topicRulePayload
- The rule payload.
Request Lenses
createTopicRule_tags :: Lens' CreateTopicRule (Maybe Text) Source #
Metadata which can be used to manage the topic rule.
For URI Request parameters use format: ...key1=value1&key2=value2...
For the CLI command-line parameter use format: --tags "key1=value1&key2=value2..."
For the cli-input-json file use format: "tags": "key1=value1&key2=value2..."
createTopicRule_ruleName :: Lens' CreateTopicRule Text Source #
The name of the rule.
createTopicRule_topicRulePayload :: Lens' CreateTopicRule TopicRulePayload Source #
The rule payload.
Destructuring the Response
data CreateTopicRuleResponse Source #
See: newCreateTopicRuleResponse
smart constructor.
Instances
Eq CreateTopicRuleResponse Source # | |
Defined in Amazonka.IoT.CreateTopicRule | |
Read CreateTopicRuleResponse Source # | |
Show CreateTopicRuleResponse Source # | |
Defined in Amazonka.IoT.CreateTopicRule showsPrec :: Int -> CreateTopicRuleResponse -> ShowS # show :: CreateTopicRuleResponse -> String # showList :: [CreateTopicRuleResponse] -> ShowS # | |
Generic CreateTopicRuleResponse Source # | |
Defined in Amazonka.IoT.CreateTopicRule type Rep CreateTopicRuleResponse :: Type -> Type # | |
NFData CreateTopicRuleResponse Source # | |
Defined in Amazonka.IoT.CreateTopicRule rnf :: CreateTopicRuleResponse -> () # | |
type Rep CreateTopicRuleResponse Source # | |
newCreateTopicRuleResponse :: CreateTopicRuleResponse Source #
Create a value of CreateTopicRuleResponse
with all optional fields omitted.
Use generic-lens or optics to modify other optional fields.