@kensio/yulin 1.20.17 → 1.21.1

package/docs/services/cloudformation/README.md

@@ -3353,7 +3353,7 @@ const stack = await simAws.cloudFormation().deployTemplate({
         Type: "AWS::S3::Bucket",
         Properties: {
           BucketName: "uploads",
-          VersioningConfiguration: { Status: "Enabled" },
+          AccelerateConfiguration: { AccelerationStatus: "Enabled" },
         },
       },
     },
@@ -3362,15 +3362,15 @@ const stack = await simAws.cloudFormation().deployTemplate({
 
 await stack.waitForDeployComplete();
 
-// The Bucket exists and is usable, unversioned.
+// The Bucket exists and is usable, without transfer acceleration.
 console.log(stack.getResource("UploadsBucket")?.deployed);
 // true
 
 for (const ignored of stack.ignoredProperties) {
   console.log(ignored.logicalId, ignored.path, ignored.reason);
-  // "UploadsBucket VersioningConfiguration VersioningConfiguration is a real
-  //  AWS::S3::Bucket property simulated S3 does not act on: Object versions
-  //  are not simulated, ..."
+  // "UploadsBucket AccelerateConfiguration AccelerateConfiguration is a real
+  //  AWS::S3::Bucket property simulated S3 does not act on: transfer
+  //  acceleration is not simulated"
 }
 ```
 
@@ -3393,7 +3393,7 @@ A property name AWS has never had is recorded the same way, and never fails the
 property AWS added after this simulator read the docs look identical from here, and a Resource that
 deploys with the unread name reported is more useful than a stack that fails over either.
 
-Two things are still refused outright, and fail the Resource:
+Three things are still refused outright, and fail the Resource:
 
 - A property that leaves nothing coherent to create, such as an `AWS::S3::Bucket` whose `BucketName`
   is some type other than a string, or an `AWS::DynamoDB::GlobalTable` whose replica list omits the
@@ -3401,6 +3401,16 @@ Two things are still refused outright, and fail the Resource:
 - A value the simulated service itself refuses, in the same words an SDK caller gets. An
   `AWS::SQS::Queue` with `FifoQueue: true` is one. A FIFO queue is named `<name>.fifo`, which
   simulated SQS refuses, leaving no queue to create under the name the template gave it.
+- A value real AWS answers with a 400, on a property that is skipped. Nothing acts on the property
+  either way, and what it says is read far enough to catch a template CloudFormation will reject. A
+  value that passes is recorded like any other skipped property. One that fails takes the Resource
+  with it, before anything is recorded against it. Two properties do this today. An
+  `AWS::S3::Bucket` `ReplicationConfiguration` is checked against the constraints the S3 API
+  documents, covered under
+  [Buckets from CloudFormation](https://yulinsim.dev/services/s3/#buckets-from-cloudformation "Buckets from CloudFormation"),
+  and an `AWS::SQS::Queue` `KmsDataKeyReusePeriodSeconds` against the minute to a day real SQS
+  accepts, covered under
+  [Deploying a queue from CloudFormation](https://yulinsim.dev/services/sqs/#deploying-a-queue-from-cloudformation "Deploying a queue from CloudFormation").
 
 Properties nothing simulated could tell apart are left off the list. There is no simulated KMS and
 Object bytes are stored as they arrive. An `AWS::S3::Bucket` carrying `BucketEncryption` and `Tags`,
@@ -3518,7 +3528,8 @@ The resource types it creates are:
 - `AWS::CertificateManager::Certificate`
 - `AWS::CloudFormation::WaitConditionHandle`
 - `AWS::CloudFront::Distribution`, `AWS::CloudFront::Function`,
-  `AWS::CloudFront::ResponseHeadersPolicy` and `AWS::CloudFront::CachePolicy`
+  `AWS::CloudFront::ResponseHeadersPolicy`, `AWS::CloudFront::CachePolicy` and
+  `AWS::CloudFront::OriginRequestPolicy`
 - `AWS::CloudWatch::Alarm`
 - `AWS::Cognito::UserPool`, `AWS::Cognito::UserPoolClient` and
   `AWS::Cognito::UserPoolGroup`