pub fn identity_source(mut self, input: impl Into<std::string::String>) -> Self {
            let mut v = self.identity_source.unwrap_or_default();
            v.push(input.into());
            self.identity_source = Some(v);
            self
        }
/// Appends an item to `identity_source`.
///
/// To override the contents of this collection use [`set_identity_source`](Self::set_identity_source).
///
/// <p>The identity source for which authorization is requested.</p>
/// <p>For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see <a href="https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-lambda-authorizer.html">Working with AWS Lambda authorizers for HTTP APIs</a>.</p>
/// <p>For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.</p>
Appends an item to `identity_source`.
To override the contents of this collection use [`set_identity_source`](Self::set_identity_source).

The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
Appends an item to ` identity_source ` . To override the contents of this collection use [ ` set_identity_source ` ] ( Self :: set_identity_source ) . The identity source for which authorization is requested . For a REQUEST authorizer this is optional . The value is a set of one or more mapping expressions of the specified request parameters . The identity source can be headers query string parameters stage variables and context parameters . For example if an Auth header and a Name query string parameter are defined as identity sources this value is route . request . header . Auth route . request . querystring . Name for WebSocket APIs . For HTTP APIs use selection expressions prefixed with $ for example $request . header . Auth $request . querystring . Name . These parameters are used to perform runtime validation for Lambda - based authorizers by verifying all of the identity - related request parameters are present in the request not null and non - empty . Only when this is true does the authorizer invoke the authorizer Lambda function . Otherwise it returns a 401 Unauthorized response without calling the Lambda function . For HTTP APIs identity sources are also used as the cache key when caching is enabled . To learn more see Working with AWS Lambda authorizers for HTTP APIs . For JWT a single entry that specifies where to extract the JSON Web Token ( JWT ) from inbound requests . Currently only header - based and query parameter - based selections are supported for example $request . header . Authorization .
pub fn identity_source(mut self, input: impl Into<std::string::String>) -> Self {
            let mut v = self.identity_source.unwrap_or_default();
            v.push(input.into());
            self.identity_source = Some(v);
            self
        }
pub fn identity_source ( mut self , input : impl Into < std :: string :: String > ) -> Self { let mut v = self . identity_source . unwrap_or_default ( ) ; v . push ( input . into ( ) ) ; self . identity_source = Some ( v ) ; self }
Appends an item to `identity_source`.
Appends an item to ` identity_source ` .
mut self
input
impl Into<std::string::String>
mut self
input
impl Into<std::string::String>