aws-sdk 2.1651.0 → 2.1652.0

package/clients/paymentcryptographydata.js

@@ -9,6 +9,7 @@ Object.defineProperty(apiLoader.services['paymentcryptographydata'], '2022-02-03
   get: function get() {
     var model = require('../apis/payment-cryptography-data-2022-02-03.min.json');
     model.paginators = require('../apis/payment-cryptography-data-2022-02-03.paginators.json').pagination;
+    model.waiters = require('../apis/payment-cryptography-data-2022-02-03.waiters2.json').waiters;
     return model;
   },
   enumerable: true,

package/clients/wafv2.d.ts

@@ -1777,7 +1777,7 @@ declare namespace WAFV2 {
      */
     MatchScope: JsonMatchScope;
     /**
-     * What WAF should do if it fails to completely parse the JSON body. The options are the following:    EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.    MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.    NO_MATCH - Treat the web request as not matching the rule statement.   If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.  WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.  WAF parses the JSON in the following examples as two valid key, value pairs:    Missing comma: {"key1":"value1""key2":"value2"}    Missing colon: {"key1":"value1","key2""value2"}    Extra colons: {"key1"::"value1","key2""value2"}   
+     * What WAF should do if it fails to completely parse the JSON body. The options are the following:    EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.    MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.    NO_MATCH - Treat the web request as not matching the rule statement.   If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.   WAF parsing doesn't fully validate the input JSON string, so parsing can succeed even for invalid JSON. When parsing succeeds, WAF doesn't apply the fallback behavior. For more information, see JSON body in the WAF Developer Guide. 
      */
     InvalidFallbackBehavior?: BodyParsingFallbackBehavior;
     /**

package/dist/aws-sdk-core-react-native.js

@@ -83,7 +83,7 @@ return /******/ (function(modules) { // webpackBootstrap
 	  /**
 	   * @constant
 	   */
-	  VERSION: '2.1651.0',
+	  VERSION: '2.1652.0',
 
 	  /**
 	   * @api private