text: ﻿/**
   * Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
   * SPDX-License-Identifier: Apache-2.0.
   */
  
  #pragma once
  #include <aws/cognito-idp/CognitoIdentityProvider_EXPORTS.h>
  #include <aws/cognito-idp/CognitoIdentityProviderRequest.h>
  #include <aws/core/utils/memory/stl/AWSString.h>
  #include <aws/cognito-idp/model/UserContextDataType.h>
  #include <aws/cognito-idp/model/AnalyticsMetadataType.h>
  #include <aws/core/utils/memory/stl/AWSMap.h>
  #include <utility>
  
  namespace Aws
  {
  namespace CognitoIdentityProvider
  {
  namespace Model
  {
  
    /**
     * <p>Represents the request to resend the confirmation code.</p><p><h3>See
     * Also:</h3>   <a
     * href="http://docs.aws.amazon.com/goto/WebAPI/cognito-idp-2016-04-18/ResendConfirmationCodeRequest">AWS
     * API Reference</a></p>
     */
    class AWS_COGNITOIDENTITYPROVIDER_API ResendConfirmationCodeRequest : public CognitoIdentityProviderRequest
    {
    public:
      ResendConfirmationCodeRequest();
  
      // Service request name is the Operation name which will send this request out,
      // each operation should has unique request name, so that we can get operation's name from this request.
      // Note: this is not true for response, multiple operations may have the same response name,
      // so we can not get operation's name from response.
      inline virtual const char* GetServiceRequestName() const override { return "ResendConfirmationCode"; }
  
      Aws::String SerializePayload() const override;
  
      Aws::Http::HeaderValueCollection GetRequestSpecificHeaders() const override;
  
  
      /**
       * <p>The ID of the client associated with the user pool.</p>
       */
      inline const Aws::String& GetClientId() const{ return m_clientId; }
  
      /**
       * <p>The ID of the client associated with the user pool.</p>
       */
      inline bool ClientIdHasBeenSet() const { return m_clientIdHasBeenSet; }
  
      /**
       * <p>The ID of the client associated with the user pool.</p>
       */
      inline void SetClientId(const Aws::String& value) { m_clientIdHasBeenSet = true; m_clientId = value; }
  
      /**
       * <p>The ID of the client associated with the user pool.</p>
       */
      inline void SetClientId(Aws::String&& value) { m_clientIdHasBeenSet = true; m_clientId = std::move(value); }
  
      /**
       * <p>The ID of the client associated with the user pool.</p>
       */
      inline void SetClientId(const char* value) { m_clientIdHasBeenSet = true; m_clientId.assign(value); }
  
      /**
       * <p>The ID of the client associated with the user pool.</p>
       */
      inline ResendConfirmationCodeRequest& WithClientId(const Aws::String& value) { SetClientId(value); return *this;}
  
      /**
       * <p>The ID of the client associated with the user pool.</p>
       */
      inline ResendConfirmationCodeRequest& WithClientId(Aws::String&& value) { SetClientId(std::move(value)); return *this;}
  
      /**
       * <p>The ID of the client associated with the user pool.</p>
       */
      inline ResendConfirmationCodeRequest& WithClientId(const char* value) { SetClientId(value); return *this;}
  
  
      /**
       * <p>A keyed-hash message authentication code (HMAC) calculated using the secret
       * key of a user pool client and username plus the client ID in the message.</p>
       */
      inline const Aws::String& GetSecretHash() const{ return m_secretHash; }
  
      /**
       * <p>A keyed-hash message authentication code (HMAC) calculated using the secret
       * key of a user pool client and username plus the client ID in the message.</p>
       */
      inline bool SecretHashHasBeenSet() const { return m_secretHashHasBeenSet; }
  
      /**
       * <p>A keyed-hash message authentication code (HMAC) calculated using the secret
       * key of a user pool client and username plus the client ID in the message.</p>
       */
      inline void SetSecretHash(const Aws::String& value) { m_secretHashHasBeenSet = true; m_secretHash = value; }
  
      /**
       * <p>A keyed-hash message authentication code (HMAC) calculated using the secret
       * key of a user pool client and username plus the client ID in the message.</p>
       */
      inline void SetSecretHash(Aws::String&& value) { m_secretHashHasBeenSet = true; m_secretHash = std::move(value); }
  
      /**
       * <p>A keyed-hash message authentication code (HMAC) calculated using the secret
       * key of a user pool client and username plus the client ID in the message.</p>
       */
      inline void SetSecretHash(const char* value) { m_secretHashHasBeenSet = true; m_secretHash.assign(value); }
  
      /**
       * <p>A keyed-hash message authentication code (HMAC) calculated using the secret
       * key of a user pool client and username plus the client ID in the message.</p>
       */
      inline ResendConfirmationCodeRequest& WithSecretHash(const Aws::String& value) { SetSecretHash(value); return *this;}
  
      /**
       * <p>A keyed-hash message authentication code (HMAC) calculated using the secret
       * key of a user pool client and username plus the client ID in the message.</p>
       */
      inline ResendConfirmationCodeRequest& WithSecretHash(Aws::String&& value) { SetSecretHash(std::move(value)); return *this;}
  
      /**
       * <p>A keyed-hash message authentication code (HMAC) calculated using the secret
       * key of a user pool client and username plus the client ID in the message.</p>
       */
      inline ResendConfirmationCodeRequest& WithSecretHash(const char* value) { SetSecretHash(value); return *this;}
  
  
      /**
       * <p>Contextual data such as the user's device fingerprint, IP address, or
       * location used for evaluating the risk of an unexpected event by Amazon Cognito
       * advanced security.</p>
       */
      inline const UserContextDataType& GetUserContextData() const{ return m_userContextData; }
  
      /**
       * <p>Contextual data such as the user's device fingerprint, IP address, or
       * location used for evaluating the risk of an unexpected event by Amazon Cognito
       * advanced security.</p>
       */
      inline bool UserContextDataHasBeenSet() const { return m_userContextDataHasBeenSet; }
  
      /**
       * <p>Contextual data such as the user's device fingerprint, IP address, or
       * location used for evaluating the risk of an unexpected event by Amazon Cognito
       * advanced security.</p>
       */
      inline void SetUserContextData(const UserContextDataType& value) { m_userContextDataHasBeenSet = true; m_userContextData = value; }
  
      /**
       * <p>Contextual data such as the user's device fingerprint, IP address, or
       * location used for evaluating the risk of an unexpected event by Amazon Cognito
       * advanced security.</p>
       */
      inline void SetUserContextData(UserContextDataType&& value) { m_userContextDataHasBeenSet = true; m_userContextData = std::move(value); }
  
      /**
       * <p>Contextual data such as the user's device fingerprint, IP address, or
       * location used for evaluating the risk of an unexpected event by Amazon Cognito
       * advanced security.</p>
       */
      inline ResendConfirmationCodeRequest& WithUserContextData(const UserContextDataType& value) { SetUserContextData(value); return *this;}
  
      /**
       * <p>Contextual data such as the user's device fingerprint, IP address, or
       * location used for evaluating the risk of an unexpected event by Amazon Cognito
       * advanced security.</p>
       */
      inline ResendConfirmationCodeRequest& WithUserContextData(UserContextDataType&& value) { SetUserContextData(std::move(value)); return *this;}
  
  
      /**
       * <p>The user name of the user to whom you wish to resend a confirmation code.</p>
       */
      inline const Aws::String& GetUsername() const{ return m_username; }
  
      /**
       * <p>The user name of the user to whom you wish to resend a confirmation code.</p>
       */
      inline bool UsernameHasBeenSet() const { return m_usernameHasBeenSet; }
  
      /**
       * <p>The user name of the user to whom you wish to resend a confirmation code.</p>
       */
      inline void SetUsername(const Aws::String& value) { m_usernameHasBeenSet = true; m_username = value; }
  
      /**
       * <p>The user name of the user to whom you wish to resend a confirmation code.</p>
       */
      inline void SetUsername(Aws::String&& value) { m_usernameHasBeenSet = true; m_username = std::move(value); }
  
      /**
       * <p>The user name of the user to whom you wish to resend a confirmation code.</p>
       */
      inline void SetUsername(const char* value) { m_usernameHasBeenSet = true; m_username.assign(value); }
  
      /**
       * <p>The user name of the user to whom you wish to resend a confirmation code.</p>
       */
      inline ResendConfirmationCodeRequest& WithUsername(const Aws::String& value) { SetUsername(value); return *this;}
  
      /**
       * <p>The user name of the user to whom you wish to resend a confirmation code.</p>
       */
      inline ResendConfirmationCodeRequest& WithUsername(Aws::String&& value) { SetUsername(std::move(value)); return *this;}
  
      /**
       * <p>The user name of the user to whom you wish to resend a confirmation code.</p>
       */
      inline ResendConfirmationCodeRequest& WithUsername(const char* value) { SetUsername(value); return *this;}
  
  
      /**
       * <p>The Amazon Pinpoint analytics metadata for collecting metrics for
       * <code>ResendConfirmationCode</code> calls.</p>
       */
      inline const AnalyticsMetadataType& GetAnalyticsMetadata() const{ return m_analyticsMetadata; }
  
      /**
       * <p>The Amazon Pinpoint analytics metadata for collecting metrics for
       * <code>ResendConfirmationCode</code> calls.</p>
       */
      inline bool AnalyticsMetadataHasBeenSet() const { return m_analyticsMetadataHasBeenSet; }
  
      /**
       * <p>The Amazon Pinpoint analytics metadata for collecting metrics for
       * <code>ResendConfirmationCode</code> calls.</p>
       */
      inline void SetAnalyticsMetadata(const AnalyticsMetadataType& value) { m_analyticsMetadataHasBeenSet = true; m_analyticsMetadata = value; }
  
      /**
       * <p>The Amazon Pinpoint analytics metadata for collecting metrics for
       * <code>ResendConfirmationCode</code> calls.</p>
       */
      inline void SetAnalyticsMetadata(AnalyticsMetadataType&& value) { m_analyticsMetadataHasBeenSet = true; m_analyticsMetadata = std::move(value); }
  
      /**
       * <p>The Amazon Pinpoint analytics metadata for collecting metrics for
       * <code>ResendConfirmationCode</code> calls.</p>
       */
      inline ResendConfirmationCodeRequest& WithAnalyticsMetadata(const AnalyticsMetadataType& value) { SetAnalyticsMetadata(value); return *this;}
  
      /**
       * <p>The Amazon Pinpoint analytics metadata for collecting metrics for
       * <code>ResendConfirmationCode</code> calls.</p>
       */
      inline ResendConfirmationCodeRequest& WithAnalyticsMetadata(AnalyticsMetadataType&& value) { SetAnalyticsMetadata(std::move(value)); return *this;}
  
  
      /**
       * <p>A map of custom key-value pairs that you can provide as input for any custom
       * workflows that this action triggers. </p> <p>You create custom workflows by
       * assigning AWS Lambda functions to user pool triggers. When you use the
       * ResendConfirmationCode API action, Amazon Cognito invokes the function that is
       * assigned to the <i>custom message</i> trigger. When Amazon Cognito invokes this
       * function, it passes a JSON payload, which the function receives as input. This
       * payload contains a <code>clientMetadata</code> attribute, which provides the
       * data that you assigned to the ClientMetadata parameter in your
       * ResendConfirmationCode request. In your function code in AWS Lambda, you can
       * process the <code>clientMetadata</code> value to enhance your workflow for your
       * specific needs.</p> <p>For more information, see <a
       * href="https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-working-with-aws-lambda-triggers.html">Customizing
       * User Pool Workflows with Lambda Triggers</a> in the <i>Amazon Cognito Developer
       * Guide</i>.</p> <note> <p>Take the following limitations into consideration when
       * you use the ClientMetadata parameter:</p> <ul> <li> <p>Amazon Cognito does not
       * store the ClientMetadata value. This data is available only to AWS Lambda
       * triggers that are assigned to a user pool to support custom workflows. If your
       * user pool configuration does not include triggers, the ClientMetadata parameter
       * serves no purpose.</p> </li> <li> <p>Amazon Cognito does not validate the
       * ClientMetadata value.</p> </li> <li> <p>Amazon Cognito does not encrypt the the
       * ClientMetadata value, so don't use it to provide sensitive information.</p>
       * </li> </ul> </note>
       */
      inline const Aws::Map<Aws::String, Aws::String>& GetClientMetadata() const{ return m_clientMetadata; }
  
      /**
       * <p>A map of custom key-value pairs that you can provide as input for any custom
       * workflows that this action triggers. </p> <p>You create custom workflows by
       * assigning AWS Lambda functions to user pool triggers. When you use the
       * ResendConfirmationCode API action, Amazon Cognito invokes the function that is
       * assigned to the <i>custom message</i> trigger. When Amazon Cognito invokes this
       * function, it passes a JSON payload, which the function receives as input. This
       * payload contains a <code>clientMetadata</code> attribute, which provides the
       * data that you assigned to the ClientMetadata parameter in your
       * ResendConfirmationCode request. In your function code in AWS Lambda, you can
       * process the <code>clientMetadata</code> value to enhance your workflow for your
       * specific needs.</p> <p>For more information, see <a
       * href="https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-working-with-aws-lambda-triggers.html">Customizing
       * User Pool Workflows with Lambda Triggers</a> in the <i>Amazon Cognito Developer
       * Guide</i>.</p> <note> <p>Take the following limitations into consideration when
       * you use the ClientMetadata parameter:</p> <ul> <li> <p>Amazon Cognito does not
       * store the ClientMetadata value. This data is available only to AWS Lambda
       * triggers that are assigned to a user pool to support custom workflows. If your
       * user pool configuration does not include triggers, the ClientMetadata parameter
       * serves no purpose.</p> </li> <li> <p>Amazon Cognito does not validate the
       * ClientMetadata value.</p> </li> <li> <p>Amazon Cognito does not encrypt the the
       * ClientMetadata value, so don't use it to provide sensitive information.</p>
       * </li> </ul> </note>
       */
      inline bool ClientMetadataHasBeenSet() const { return m_clientMetadataHasBeenSet; }
  
      /**
       * <p>A map of custom key-value pairs that you can provide as input for any custom
       * workflows that this action triggers. </p> <p>You create custom workflows by
       * assigning AWS Lambda functions to user pool triggers. When you use the
       * ResendConfirmationCode API action, Amazon Cognito invokes the function that is
       * assigned to the <i>custom message</i> trigger. When Amazon Cognito invokes this
       * function, it passes a JSON payload, which the function receives as input. This
       * payload contains a <code>clientMetadata</code> attribute, which provides the
       * data that you assigned to the ClientMetadata parameter in your
       * ResendConfirmationCode request. In your function code in AWS Lambda, you can
       * process the <code>clientMetadata</code> value to enhance your workflow for your
       * specific needs.</p> <p>For more information, see <a
       * href="https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-working-with-aws-lambda-triggers.html">Customizing
       * User Pool Workflows with Lambda Triggers</a> in the <i>Amazon Cognito Developer
       * Guide</i>.</p> <note> <p>Take the following limitations into consideration when
       * you use the ClientMetadata parameter:</p> <ul> <li> <p>Amazon Cognito does not
       * store the ClientMetadata value. This data is available only to AWS Lambda
       * triggers that are assigned to a user pool to support custom workflows. If your
       * user pool configuration does not include triggers, the ClientMetadata parameter
       * serves no purpose.</p> </li> <li> <p>Amazon Cognito does not validate the
       * ClientMetadata value.</p> </li> <li> <p>Amazon Cognito does not encrypt the the
       * ClientMetadata value, so don't use it to provide sensitive information.</p>
       * </li> </ul> </note>
       */
      inline void SetClientMetadata(const Aws::Map<Aws::String, Aws::String>& value) { m_clientMetadataHasBeenSet = true; m_clientMetadata = value; }
  
      /**
       * <p>A map of custom key-value pairs that you can provide as input for any custom
       * workflows that this action triggers. </p> <p>You create custom workflows by
       * assigning AWS Lambda functions to user pool triggers. When you use the
       * ResendConfirmationCode API action, Amazon Cognito invokes the function that is
       * assigned to the <i>custom message</i> trigger. When Amazon Cognito invokes this
       * function, it passes a JSON payload, which the function receives as input. This
       * payload contains a <code>clientMetadata</code> attribute, which provides the
       * data that you assigned to the ClientMetadata parameter in your
       * ResendConfirmationCode request. In your function code in AWS Lambda, you can
       * process the <code>clientMetadata</code> value to enhance your workflow for your
       * specific needs.</p> <p>For more information, see <a
       * href="https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-working-with-aws-lambda-triggers.html">Customizing
       * User Pool Workflows with Lambda Triggers</a> in the <i>Amazon Cognito Developer
       * Guide</i>.</p> <note> <p>Take the following limitations into consideration when
       * you use the ClientMetadata parameter:</p> <ul> <li> <p>Amazon Cognito does not
       * store the ClientMetadata value. This data is available only to AWS Lambda
       * triggers that are assigned to a user pool to support custom workflows. If your
       * user pool configuration does not include triggers, the ClientMetadata parameter
       * serves no purpose.</p> </li> <li> <p>Amazon Cognito does not validate the
       * ClientMetadata value.</p> </li> <li> <p>Amazon Cognito does not encrypt the the
       * ClientMetadata value, so don't use it to provide sensitive information.</p>
       * </li> </ul> </note>
       */
      inline void SetClientMetadata(Aws::Map<Aws::String, Aws::String>&& value) { m_clientMetadataHasBeenSet = true; m_clientMetadata = std::move(value); }
  
      /**
       * <p>A map of custom key-value pairs that you can provide as input for any custom
       * workflows that this action triggers. </p> <p>You create custom workflows by
       * assigning AWS Lambda functions to user pool triggers. When you use the
       * ResendConfirmationCode API action, Amazon Cognito invokes the function that is
       * assigned to the <i>custom message</i> trigger. When Amazon Cognito invokes this
       * function, it passes a JSON payload, which the function receives as input. This
       * payload contains a <code>clientMetadata</code> attribute, which provides the
       * data that you assigned to the ClientMetadata parameter in your
       * ResendConfirmationCode request. In your function code in AWS Lambda, you can
       * process the <code>clientMetadata</code> value to enhance your workflow for your
       * specific needs.</p> <p>For more information, see <a
       * href="https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-working-with-aws-lambda-triggers.html">Customizing
       * User Pool Workflows with Lambda Triggers</a> in the <i>Amazon Cognito Developer
       * Guide</i>.</p> <note> <p>Take the following limitations into consideration when
       * you use the ClientMetadata parameter:</p> <ul> <li> <p>Amazon Cognito does not
       * store the ClientMetadata value. This data is available only to AWS Lambda
       * triggers that are assigned to a user pool to support custom workflows. If your
       * user pool configuration does not include triggers, the ClientMetadata parameter
       * serves no purpose.</p> </li> <li> <p>Amazon Cognito does not validate the
       * ClientMetadata value.</p> </li> <li> <p>Amazon Cognito does not encrypt the the
       * ClientMetadata value, so don't use it to provide sensitive information.</p>
       * </li> </ul> </note>
       */
      inline ResendConfirmationCodeRequest& WithClientMetadata(const Aws::Map<Aws::String, Aws::String>& value) { SetClientMetadata(value); return *this;}
  
      /**
       * <p>A map of custom key-value pairs that you can provide as input for any custom
       * workflows that this action triggers. </p> <p>You create custom workflows by
       * assigning AWS Lambda functions to user pool triggers. When you use the
       * ResendConfirmationCode API action, Amazon Cognito invokes the function that is
       * assigned to the <i>custom message</i> trigger. When Amazon Cognito invokes this
       * function, it passes a JSON payload, which the function receives as input. This
       * payload contains a <code>clientMetadata</code> attribute, which provides the
       * data that you assigned to the ClientMetadata parameter in your
       * ResendConfirmationCode request. In your function code in AWS Lambda, you can
       * process the <code>clientMetadata</code> value to enhance your workflow for your
       * specific needs.</p> <p>For more information, see <a
       * href="https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-working-with-aws-lambda-triggers.html">Customizing
       * User Pool Workflows with Lambda Triggers</a> in the <i>Amazon Cognito Developer
       * Guide</i>.</p> <note> <p>Take the following limitations into consideration when
       * you use the ClientMetadata parameter:</p> <ul> <li> <p>Amazon Cognito does not
       * store the ClientMetadata value. This data is available only to AWS Lambda
       * triggers that are assigned to a user pool to support custom workflows. If your
       * user pool configuration does not include triggers, the ClientMetadata parameter
       * serves no purpose.</p> </li> <li> <p>Amazon Cognito does not validate the
       * ClientMetadata value.</p> </li> <li> <p>Amazon Cognito does not encrypt the the
       * ClientMetadata value, so don't use it to provide sensitive information.</p>
       * </li> </ul> </note>
       */
      inline ResendConfirmationCodeRequest& WithClientMetadata(Aws::Map<Aws::String, Aws::String>&& value) { SetClientMetadata(std::move(value)); return *this;}
  
      /**
       * <p>A map of custom key-value pairs that you can provide as input for any custom
       * workflows that this action triggers. </p> <p>You create custom workflows by
       * assigning AWS Lambda functions to user pool triggers. When you use the
       * ResendConfirmationCode API action, Amazon Cognito invokes the function that is
       * assigned to the <i>custom message</i> trigger. When Amazon Cognito invokes this
       * function, it passes a JSON payload, which the function receives as input. This
       * payload contains a <code>clientMetadata</code> attribute, which provides the
       * data that you assigned to the ClientMetadata parameter in your
       * ResendConfirmationCode request. In your function code in AWS Lambda, you can
       * process the <code>clientMetadata</code> value to enhance your workflow for your
       * specific needs.</p> <p>For more information, see <a
       * href="https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-working-with-aws-lambda-triggers.html">Customizing
       * User Pool Workflows with Lambda Triggers</a> in the <i>Amazon Cognito Developer
       * Guide</i>.</p> <note> <p>Take the following limitations into consideration when
       * you use the ClientMetadata parameter:</p> <ul> <li> <p>Amazon Cognito does not
       * store the ClientMetadata value. This data is available only to AWS Lambda
       * triggers that are assigned to a user pool to support custom workflows. If your
       * user pool configuration does not include triggers, the ClientMetadata parameter
       * serves no purpose.</p> </li> <li> <p>Amazon Cognito does not validate the
       * ClientMetadata value.</p> </li> <li> <p>Amazon Cognito does not encrypt the the
       * ClientMetadata value, so don't use it to provide sensitive information.</p>
       * </li> </ul> </note>
       */
      inline ResendConfirmationCodeRequest& AddClientMetadata(const Aws::String& key, const Aws::String& value) { m_clientMetadataHasBeenSet = true; m_clientMetadata.emplace(key, value); return *this; }
  
      /**
       * <p>A map of custom key-value pairs that you can provide as input for any custom
       * workflows that this action triggers. </p> <p>You create custom workflows by
       * assigning AWS Lambda functions to user pool triggers. When you use the
       * ResendConfirmationCode API action, Amazon Cognito invokes the function that is
       * assigned to the <i>custom message</i> trigger. When Amazon Cognito invokes this
       * function, it passes a JSON payload, which the function receives as input. This
       * payload contains a <code>clientMetadata</code> attribute, which provides the
       * data that you assigned to the ClientMetadata parameter in your
       * ResendConfirmationCode request. In your function code in AWS Lambda, you can
       * process the <code>clientMetadata</code> value to enhance your workflow for your
       * specific needs.</p> <p>For more information, see <a
       * href="https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-working-with-aws-lambda-triggers.html">Customizing
       * User Pool Workflows with Lambda Triggers</a> in the <i>Amazon Cognito Developer
       * Guide</i>.</p> <note> <p>Take the following limitations into consideration when
       * you use the ClientMetadata parameter:</p> <ul> <li> <p>Amazon Cognito does not
       * store the ClientMetadata value. This data is available only to AWS Lambda
       * triggers that are assigned to a user pool to support custom workflows. If your
       * user pool configuration does not include triggers, the ClientMetadata parameter
       * serves no purpose.</p> </li> <li> <p>Amazon Cognito does not validate the
       * ClientMetadata value.</p> </li> <li> <p>Amazon Cognito does not encrypt the the
       * ClientMetadata value, so don't use it to provide sensitive information.</p>
       * </li> </ul> </note>
       */
      inline ResendConfirmationCodeRequest& AddClientMetadata(Aws::String&& key, const Aws::String& value) { m_clientMetadataHasBeenSet = true; m_clientMetadata.emplace(std::move(key), value); return *this; }
  
      /**
       * <p>A map of custom key-value pairs that you can provide as input for any custom
       * workflows that this action triggers. </p> <p>You create custom workflows by
       * assigning AWS Lambda functions to user pool triggers. When you use the
       * ResendConfirmationCode API action, Amazon Cognito invokes the function that is
       * assigned to the <i>custom message</i> trigger. When Amazon Cognito invokes this
       * function, it passes a JSON payload, which the function receives as input. This
       * payload contains a <code>clientMetadata</code> attribute, which provides the
       * data that you assigned to the ClientMetadata parameter in your
       * ResendConfirmationCode request. In your function code in AWS Lambda, you can
       * process the <code>clientMetadata</code> value to enhance your workflow for your
       * specific needs.</p> <p>For more information, see <a
       * href="https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-working-with-aws-lambda-triggers.html">Customizing
       * User Pool Workflows with Lambda Triggers</a> in the <i>Amazon Cognito Developer
       * Guide</i>.</p> <note> <p>Take the following limitations into consideration when
       * you use the ClientMetadata parameter:</p> <ul> <li> <p>Amazon Cognito does not
       * store the ClientMetadata value. This data is available only to AWS Lambda
       * triggers that are assigned to a user pool to support custom workflows. If your
       * user pool configuration does not include triggers, the ClientMetadata parameter
       * serves no purpose.</p> </li> <li> <p>Amazon Cognito does not validate the
       * ClientMetadata value.</p> </li> <li> <p>Amazon Cognito does not encrypt the the
       * ClientMetadata value, so don't use it to provide sensitive information.</p>
       * </li> </ul> </note>
       */
      inline ResendConfirmationCodeRequest& AddClientMetadata(const Aws::String& key, Aws::String&& value) { m_clientMetadataHasBeenSet = true; m_clientMetadata.emplace(key, std::move(value)); return *this; }
  
      /**
       * <p>A map of custom key-value pairs that you can provide as input for any custom
       * workflows that this action triggers. </p> <p>You create custom workflows by
       * assigning AWS Lambda functions to user pool triggers. When you use the
       * ResendConfirmationCode API action, Amazon Cognito invokes the function that is
       * assigned to the <i>custom message</i> trigger. When Amazon Cognito invokes this
       * function, it passes a JSON payload, which the function receives as input. This
       * payload contains a <code>clientMetadata</code> attribute, which provides the
       * data that you assigned to the ClientMetadata parameter in your
       * ResendConfirmationCode request. In your function code in AWS Lambda, you can
       * process the <code>clientMetadata</code> value to enhance your workflow for your
       * specific needs.</p> <p>For more information, see <a
       * href="https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-working-with-aws-lambda-triggers.html">Customizing
       * User Pool Workflows with Lambda Triggers</a> in the <i>Amazon Cognito Developer
       * Guide</i>.</p> <note> <p>Take the following limitations into consideration when
       * you use the ClientMetadata parameter:</p> <ul> <li> <p>Amazon Cognito does not
       * store the ClientMetadata value. This data is available only to AWS Lambda
       * triggers that are assigned to a user pool to support custom workflows. If your
       * user pool configuration does not include triggers, the ClientMetadata parameter
       * serves no purpose.</p> </li> <li> <p>Amazon Cognito does not validate the
       * ClientMetadata value.</p> </li> <li> <p>Amazon Cognito does not encrypt the the
       * ClientMetadata value, so don't use it to provide sensitive information.</p>
       * </li> </ul> </note>
       */
      inline ResendConfirmationCodeRequest& AddClientMetadata(Aws::String&& key, Aws::String&& value) { m_clientMetadataHasBeenSet = true; m_clientMetadata.emplace(std::move(key), std::move(value)); return *this; }
  
      /**
       * <p>A map of custom key-value pairs that you can provide as input for any custom
       * workflows that this action triggers. </p> <p>You create custom workflows by
       * assigning AWS Lambda functions to user pool triggers. When you use the
       * ResendConfirmationCode API action, Amazon Cognito invokes the function that is
       * assigned to the <i>custom message</i> trigger. When Amazon Cognito invokes this
       * function, it passes a JSON payload, which the function receives as input. This
       * payload contains a <code>clientMetadata</code> attribute, which provides the
       * data that you assigned to the ClientMetadata parameter in your
       * ResendConfirmationCode request. In your function code in AWS Lambda, you can
       * process the <code>clientMetadata</code> value to enhance your workflow for your
       * specific needs.</p> <p>For more information, see <a
       * href="https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-working-with-aws-lambda-triggers.html">Customizing
       * User Pool Workflows with Lambda Triggers</a> in the <i>Amazon Cognito Developer
       * Guide</i>.</p> <note> <p>Take the following limitations into consideration when
       * you use the ClientMetadata parameter:</p> <ul> <li> <p>Amazon Cognito does not
       * store the ClientMetadata value. This data is available only to AWS Lambda
       * triggers that are assigned to a user pool to support custom workflows. If your
       * user pool configuration does not include triggers, the ClientMetadata parameter
       * serves no purpose.</p> </li> <li> <p>Amazon Cognito does not validate the
       * ClientMetadata value.</p> </li> <li> <p>Amazon Cognito does not encrypt the the
       * ClientMetadata value, so don't use it to provide sensitive information.</p>
       * </li> </ul> </note>
       */
      inline ResendConfirmationCodeRequest& AddClientMetadata(const char* key, Aws::String&& value) { m_clientMetadataHasBeenSet = true; m_clientMetadata.emplace(key, std::move(value)); return *this; }
  
      /**
       * <p>A map of custom key-value pairs that you can provide as input for any custom
       * workflows that this action triggers. </p> <p>You create custom workflows by
       * assigning AWS Lambda functions to user pool triggers. When you use the
       * ResendConfirmationCode API action, Amazon Cognito invokes the function that is
       * assigned to the <i>custom message</i> trigger. When Amazon Cognito invokes this
       * function, it passes a JSON payload, which the function receives as input. This
       * payload contains a <code>clientMetadata</code> attribute, which provides the
       * data that you assigned to the ClientMetadata parameter in your
       * ResendConfirmationCode request. In your function code in AWS Lambda, you can
       * process the <code>clientMetadata</code> value to enhance your workflow for your
       * specific needs.</p> <p>For more information, see <a
       * href="https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-working-with-aws-lambda-triggers.html">Customizing
       * User Pool Workflows with Lambda Triggers</a> in the <i>Amazon Cognito Developer
       * Guide</i>.</p> <note> <p>Take the following limitations into consideration when
       * you use the ClientMetadata parameter:</p> <ul> <li> <p>Amazon Cognito does not
       * store the ClientMetadata value. This data is available only to AWS Lambda
       * triggers that are assigned to a user pool to support custom workflows. If your
       * user pool configuration does not include triggers, the ClientMetadata parameter
       * serves no purpose.</p> </li> <li> <p>Amazon Cognito does not validate the
       * ClientMetadata value.</p> </li> <li> <p>Amazon Cognito does not encrypt the the
       * ClientMetadata value, so don't use it to provide sensitive information.</p>
       * </li> </ul> </note>
       */
      inline ResendConfirmationCodeRequest& AddClientMetadata(Aws::String&& key, const char* value) { m_clientMetadataHasBeenSet = true; m_clientMetadata.emplace(std::move(key), value); return *this; }
  
      /**
       * <p>A map of custom key-value pairs that you can provide as input for any custom
       * workflows that this action triggers. </p> <p>You create custom workflows by
       * assigning AWS Lambda functions to user pool triggers. When you use the
       * ResendConfirmationCode API action, Amazon Cognito invokes the function that is
       * assigned to the <i>custom message</i> trigger. When Amazon Cognito invokes this
       * function, it passes a JSON payload, which the function receives as input. This
       * payload contains a <code>clientMetadata</code> attribute, which provides the
       * data that you assigned to the ClientMetadata parameter in your
       * ResendConfirmationCode request. In your function code in AWS Lambda, you can
       * process the <code>clientMetadata</code> value to enhance your workflow for your
       * specific needs.</p> <p>For more information, see <a
       * href="https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-working-with-aws-lambda-triggers.html">Customizing
       * User Pool Workflows with Lambda Triggers</a> in the <i>Amazon Cognito Developer
       * Guide</i>.</p> <note> <p>Take the following limitations into consideration when
       * you use the ClientMetadata parameter:</p> <ul> <li> <p>Amazon Cognito does not
       * store the ClientMetadata value. This data is available only to AWS Lambda
       * triggers that are assigned to a user pool to support custom workflows. If your
       * user pool configuration does not include triggers, the ClientMetadata parameter
       * serves no purpose.</p> </li> <li> <p>Amazon Cognito does not validate the
       * ClientMetadata value.</p> </li> <li> <p>Amazon Cognito does not encrypt the the
       * ClientMetadata value, so don't use it to provide sensitive information.</p>
       * </li> </ul> </note>
       */
      inline ResendConfirmationCodeRequest& AddClientMetadata(const char* key, const char* value) { m_clientMetadataHasBeenSet = true; m_clientMetadata.emplace(key, value); return *this; }
  
    private:
  
      Aws::String m_clientId;
      bool m_clientIdHasBeenSet;
  
      Aws::String m_secretHash;
      bool m_secretHashHasBeenSet;
  
      UserContextDataType m_userContextData;
      bool m_userContextDataHasBeenSet;
  
      Aws::String m_username;
      bool m_usernameHasBeenSet;
  
      AnalyticsMetadataType m_analyticsMetadata;
      bool m_analyticsMetadataHasBeenSet;
  
      Aws::Map<Aws::String, Aws::String> m_clientMetadata;
      bool m_clientMetadataHasBeenSet;
    };
  
  } // namespace Model
  } // namespace CognitoIdentityProvider
  } // namespace Aws
  