@kensio/yulin 1.21.0 → 1.21.2

package/dist/service/ses/index.js

@@ -8,9 +8,10 @@ export { SimSesConfigurationSet, } from "./configuration-set/sim-ses-configurati
 export { SimSesConfigurationSetStore } from "./configuration-set/sim-ses-configuration-set-store.js";
 export { SimSesSentEmail, } from "./email/sim-ses-sent-email.js";
 export { SimSesSentEmailStore } from "./email/sim-ses-sent-email-store.js";
+export { SimSesFeedbackRecorder, } from "./feedback/sim-ses-feedback-recorder.js";
 export { requiredSimSesFromAddress, simSesBareAddress, } from "./email/sim-ses-address.js";
 export { SimSesSuppressedDestination } from "./suppression/sim-ses-suppressed-destination.js";
 export { SimSesSuppressionList } from "./suppression/sim-ses-suppression-list.js";
 export { requiredSimSesSuppressionReason, } from "./suppression/sim-ses-suppression-reason.js";
 export { SimSesAccount, } from "./account/sim-ses-account.js";
-export { SimSesAlreadyExistsException, SimSesBadRequestException, SimSesError, SimSesMessageRejected, SimSesNotFoundException, SimSesSendingPausedException, SimSesUnsupportedOperationException, } from "./error/sim-ses.error.js";
+export { SimSesAlreadyExistsException, SimSesBadRequestException, SimSesError, SimSesFeedbackError, SimSesMessageRejected, SimSesNotFoundException, SimSesSendingPausedException, SimSesUnsupportedOperationException, } from "./error/sim-ses.error.js";

package/dist/service/ses/sim-ses-commands.d.ts

@@ -11,6 +11,7 @@ import { SimSesServiceSend } from "./command/send/sim-ses-service-send.js";
 import { SimSesSuppressionCommands } from "./command/suppression/sim-ses-suppression-commands.js";
 import { SimSesSuppressionList } from "./suppression/sim-ses-suppression-list.js";
 import { SimSesSentEmailStore } from "./email/sim-ses-sent-email-store.js";
+import { SimSesFeedbackRecorder } from "./feedback/sim-ses-feedback-recorder.js";
 import { SimSesConfigurationSetStore } from "./configuration-set/sim-ses-configuration-set-store.js";
 import { SimSesIdentityStore } from "./identity/sim-ses-identity-store.js";
 import { SimSesTemplateCommands } from "./command/template/sim-ses-template-commands.js";
@@ -43,6 +44,7 @@ export declare class SimSesCommands {
     readonly templateCommands: SimSesTemplateCommands;
     readonly configurationSetCommands: SimSesConfigurationSetCommands;
     readonly sendEmail: SimSesSendEmail;
+    readonly feedback: SimSesFeedbackRecorder;
     /**
      * The way another simulated service reaches this SES, which is the send
      * without the IAM authorization a caller's request goes through.

package/dist/service/ses/sim-ses-commands.js

@@ -16,6 +16,7 @@ import { SimSesVerifiedIdentityCheck } from "./command/send/sim-ses-verified-ide
 import { SimSesSuppressionCommands } from "./command/suppression/sim-ses-suppression-commands.js";
 import { SimSesSuppressionList } from "./suppression/sim-ses-suppression-list.js";
 import { SimSesSentEmailStore } from "./email/sim-ses-sent-email-store.js";
+import { SimSesFeedbackRecorder } from "./feedback/sim-ses-feedback-recorder.js";
 import { SimSesConfigurationSetStore } from "./configuration-set/sim-ses-configuration-set-store.js";
 import { SimSesIdentityStore } from "./identity/sim-ses-identity-store.js";
 import { SimSesTemplateCommands } from "./command/template/sim-ses-template-commands.js";
@@ -39,6 +40,7 @@ export class SimSesCommands {
     templateCommands;
     configurationSetCommands;
     sendEmail;
+    feedback;
     /**
      * The way another simulated service reaches this SES, which is the send
      * without the IAM authorization a caller's request goes through.
@@ -103,6 +105,13 @@ export class SimSesCommands {
             authorizer,
             clock: background,
         });
+        this.feedback = new SimSesFeedbackRecorder({
+            sent,
+            configurationSets,
+            account,
+            suppression,
+            clock: background,
+        });
         this.serviceSend = new SimSesServiceSend({
             sent,
             identityCheck,

package/dist/service/ses/sim-ses-configuration-sets.d.ts

@@ -10,10 +10,10 @@ import { SimSesSuppression } from "./sim-ses-suppression.js";
  * separate classes because one class holding every SES operation grows by a
  * method with each one added.
  *
- * A configuration set here is state and no behaviour. Its suppression reasons,
- * sending switch, delivery options and reputation switch are all held and read
- * back, and nothing acts on any of them. A send naming a set keeps the name on
- * its record and goes no further.
+ * A configuration set holds suppression reasons, the sending switch, delivery
+ * options and the reputation switch. The sending switch acts on acceptance.
+ * Suppression reasons act when feedback is recorded for an accepted message.
+ * The remaining options are held for a test to read back.
  */
 export declare abstract class SimSesConfigurationSets extends SimSesSuppression {
     /**

package/dist/service/ses/sim-ses-configuration-sets.js

@@ -7,10 +7,10 @@ import { SimSesSuppression } from "./sim-ses-suppression.js";
  * separate classes because one class holding every SES operation grows by a
  * method with each one added.
  *
- * A configuration set here is state and no behaviour. Its suppression reasons,
- * sending switch, delivery options and reputation switch are all held and read
- * back, and nothing acts on any of them. A send naming a set keeps the name on
- * its record and goes no further.
+ * A configuration set holds suppression reasons, the sending switch, delivery
+ * options and the reputation switch. The sending switch acts on acceptance.
+ * Suppression reasons act when feedback is recorded for an accepted message.
+ * The remaining options are held for a test to read back.
  */
 export class SimSesConfigurationSets extends SimSesSuppression {
     /**

package/dist/service/ses/sim-ses-suppression.d.ts

@@ -13,8 +13,9 @@ interface SimSesSuppressionProperties {
  * SES operation grows by a method with each one added, and the suppression
  * commands are the part of the API a reader can take in on their own.
  *
- * Real SES fills this list from hard bounces and complaints. Nothing bounces
- * here, so every address on it was put there by a caller.
+ * Real SES fills this list from hard bounces and complaints. A test supplies
+ * that feedback explicitly, and callers may also manage entries through the
+ * suppression commands.
  */
 export declare abstract class SimSesSuppression {
     protected readonly commands: SimSesCommands;

package/dist/service/ses/sim-ses-suppression.js

@@ -6,8 +6,9 @@
  * SES operation grows by a method with each one added, and the suppression
  * commands are the part of the API a reader can take in on their own.
  *
- * Real SES fills this list from hard bounces and complaints. Nothing bounces
- * here, so every address on it was put there by a caller.
+ * Real SES fills this list from hard bounces and complaints. A test supplies
+ * that feedback explicitly, and callers may also manage entries through the
+ * suppression commands.
  */
 export class SimSesSuppression {
     commands;

package/dist/service/ses/sim-ses-v2.d.ts

@@ -3,6 +3,8 @@ import type * as simSesCommands from "./command/sim-ses-command.types.js";
 import type { SimSesRequestOptions } from "./command/sim-ses-request-options.js";
 import type * as simSesServiceSend from "./command/send/sim-ses-service-send.js";
 import type { SimSesSentEmail } from "./email/sim-ses-sent-email.js";
+import type { SimSesFeedback } from "./feedback/sim-ses-feedback-recorder.js";
+import type { SimSesSuppressedDestination } from "./suppression/sim-ses-suppressed-destination.js";
 import type { SimSesIdentity } from "./identity/sim-ses-identity.js";
 import type { SimSesTemplate } from "./template/sim-ses-template.js";
 import { SimSesCfnResourceFactory } from "./cfn/sim-ses-cfn-resource-factory.js";
@@ -39,6 +41,17 @@ export declare class SimSesV2 extends SimSesConfigurationSets {
      * account keeps no such record, which is exactly why a test needs one.
      */
     sentEmails(): readonly SimSesSentEmail[];
+    /**
+     * Record a hard bounce or complaint for one recipient of an accepted
+     * message.
+     *
+     * Real feedback happens after SES hands a message to a mail system. A test
+     * process cannot observe that exchange, so this simulator-side operation
+     * supplies the feedback explicitly. Active feedback adds or updates the
+     * account suppression entry at the current simulated time. Inactive
+     * feedback returns undefined and leaves the list unchanged.
+     */
+    recordFeedback(feedback: SimSesFeedback): SimSesSuppressedDestination | undefined;
     /**
      * Find an identity by the address or domain it names.
      *

package/dist/service/ses/sim-ses-v2.js

@@ -38,6 +38,19 @@ export class SimSesV2 extends SimSesConfigurationSets {
     sentEmails() {
         return this.commands.sent.all;
     }
+    /**
+     * Record a hard bounce or complaint for one recipient of an accepted
+     * message.
+     *
+     * Real feedback happens after SES hands a message to a mail system. A test
+     * process cannot observe that exchange, so this simulator-side operation
+     * supplies the feedback explicitly. Active feedback adds or updates the
+     * account suppression entry at the current simulated time. Inactive
+     * feedback returns undefined and leaves the list unchanged.
+     */
+    recordFeedback(feedback) {
+        return this.commands.feedback.record(feedback);
+    }
     /**
      * Find an identity by the address or domain it names.
      *

package/dist/service/ses/suppression/sim-ses-suppressed-destination.d.ts

@@ -7,10 +7,9 @@ interface SimSesSuppressedDestinationProperties {
 /**
  * One address on an account's suppression list.
  *
- * Real SES also reports a `MessageId` and a `FeedbackId` on the address it put
- * there itself, describing the bounce or complaint that did it. Nothing
- * bounces here, so every address on this list was put there by hand and there
- * is no feedback event to point at.
+ * Real SES also reports a `MessageId` and a `FeedbackId` on an address added by
+ * delivery feedback. This simulation records the reason and time only. It
+ * does not publish or retain a feedback event.
  */
 export declare class SimSesSuppressedDestination {
     /** The address as it was given, case and all. */

package/dist/service/ses/suppression/sim-ses-suppressed-destination.js

@@ -1,10 +1,9 @@
 /**
  * One address on an account's suppression list.
  *
- * Real SES also reports a `MessageId` and a `FeedbackId` on the address it put
- * there itself, describing the bounce or complaint that did it. Nothing
- * bounces here, so every address on this list was put there by hand and there
- * is no feedback event to point at.
+ * Real SES also reports a `MessageId` and a `FeedbackId` on an address added by
+ * delivery feedback. This simulation records the reason and time only. It
+ * does not publish or retain a feedback event.
  */
 export class SimSesSuppressedDestination {
     /** The address as it was given, case and all. */

package/dist/service/ses/suppression/sim-ses-suppression-list.d.ts

@@ -3,10 +3,10 @@ import type { SimSesSuppressionReason } from "./sim-ses-suppression-reason.js";
 /**
  * The account-level suppression list of one simulated SES scope.
  *
- * Real SES fills this from hard bounces and complaints. Nothing bounces here,
- * so every address on it was put there by a caller, which is the point: an
- * application's own support tooling and operations scripts have somewhere to
- * run.
+ * Real SES fills this from hard bounces and complaints. A test supplies those
+ * events through the simulator's feedback operation. The ordinary suppression
+ * commands also manage the same entries, giving application support tooling
+ * and operations scripts somewhere to run.
  *
  * The list is region scoped, as identities and sends are. An address
  * suppressed in one region says nothing about another.

package/dist/service/ses/suppression/sim-ses-suppression-list.js

@@ -3,10 +3,10 @@ import { SimSesSuppressedDestination } from "./sim-ses-suppressed-destination.js
 /**
  * The account-level suppression list of one simulated SES scope.
  *
- * Real SES fills this from hard bounces and complaints. Nothing bounces here,
- * so every address on it was put there by a caller, which is the point: an
- * application's own support tooling and operations scripts have somewhere to
- * run.
+ * Real SES fills this from hard bounces and complaints. A test supplies those
+ * events through the simulator's feedback operation. The ordinary suppression
+ * commands also manage the same entries, giving application support tooling
+ * and operations scripts somewhere to run.
  *
  * The list is region scoped, as identities and sends are. An address
  * suppressed in one region says nothing about another.

package/dist/service/sqs/cfn/queue/sim-cfn-sqs-queue-encryption-rules.d.ts

@@ -0,0 +1,15 @@
+import type { SimCfnSkippedPropertyValue } from "../../../cloudformation/resource/ignore/sim-cfn-skipped-property.type.js";
+/**
+ * The range real SQS accepts for `KmsDataKeyReusePeriodSeconds`.
+ *
+ * Encryption itself is not simulated. The property is recorded against the
+ * Resource and the queue is created without it, and no key is ever asked for.
+ * How long the value says to reuse one is still read, because a period outside
+ * this range is one real SQS answers with `InvalidAttributeValue`, and
+ * CloudFormation fails the stack on it at CreateQueue. A queue that deployed
+ * here would report a template AWS refuses as working.
+ *
+ * The bound is the one the SQS API documents, a minute at the short end and a
+ * day at the long one.
+ */
+export declare function validateSimCfnSqsKmsDataKeyReusePeriod(declared: SimCfnSkippedPropertyValue): void;

package/dist/service/sqs/cfn/queue/sim-cfn-sqs-queue-encryption-rules.js

@@ -0,0 +1,33 @@
+const minimumReuseSeconds = 60;
+const maximumReuseSeconds = 86_400;
+/**
+ * The range real SQS accepts for `KmsDataKeyReusePeriodSeconds`.
+ *
+ * Encryption itself is not simulated. The property is recorded against the
+ * Resource and the queue is created without it, and no key is ever asked for.
+ * How long the value says to reuse one is still read, because a period outside
+ * this range is one real SQS answers with `InvalidAttributeValue`, and
+ * CloudFormation fails the stack on it at CreateQueue. A queue that deployed
+ * here would report a template AWS refuses as working.
+ *
+ * The bound is the one the SQS API documents, a minute at the short end and a
+ * day at the long one.
+ */
+export function validateSimCfnSqsKmsDataKeyReusePeriod(declared) {
+    const stated = declared.value;
+    const seconds = typeof stated === "number" || typeof stated === "string"
+        ? Number(stated)
+        : NaN;
+    if (Number.isSafeInteger(seconds) &&
+        seconds >= minimumReuseSeconds &&
+        seconds <= maximumReuseSeconds) {
+        return;
+    }
+    declared.refuse(`KmsDataKeyReusePeriodSeconds ${stringified(stated)} is outside the ` +
+        `${String(minimumReuseSeconds)} to ${String(maximumReuseSeconds)} ` +
+        `seconds real SQS accepts`);
+}
+/** The value as a refusal names it, whatever shape the template gave it. */
+function stringified(value) {
+    return typeof value === "object" ? JSON.stringify(value) : String(value);
+}

package/dist/service/sqs/cfn/queue/sim-cfn-sqs-queue-properties.d.ts

@@ -30,6 +30,22 @@ export declare class SimCfnSqsQueueProperties {
      * takes them in.
      */
     attributes(): SimSqsQueueAttributeInput;
+    /**
+     * Read one property as the string the attribute of that name carries.
+     *
+     * Five of these properties are amounts and `RedrivePolicy` is a JSON
+     * document, so the two are read differently.
+     */
+    private attributeValue;
+    /**
+     * Read a JSON document property as the string an SQS attribute carries.
+     *
+     * CloudFormation carries the document as an object, and as a string when it
+     * came from a template Parameter or from a Terraform plan holding it as one.
+     * What the document has to say is left to SQS, which refuses a bad redrive
+     * policy in its own words.
+     */
+    private documentValue;
     /**
      * Read a numeric property as the string an SQS attribute carries.
      *

package/dist/service/sqs/cfn/queue/sim-cfn-sqs-queue-properties.js

@@ -1,3 +1,6 @@
+import { jsonStringify } from "../../../../util/type-guard/json.js";
+import { isRecord } from "../../../../util/type-guard/record.js";
+import { simSqsJsonQueueAttributeNames } from "../../queue/sim-sqs-queue-attribute-specs.js";
 import { SimCfnSqsQueueName } from "./sim-cfn-sqs-queue-name.js";
 import { SimCfnSqsQueuePropertyRules, sqsQueuePropertyError, } from "./sim-cfn-sqs-queue-property-rules.js";
 /**
@@ -48,7 +51,36 @@ export class SimCfnSqsQueueProperties {
         this.rules.apply();
         return Object.fromEntries(Object.entries(this.properties)
             .filter(([name]) => this.rules.isAttributeProperty(name))
-            .map(([name, value]) => [name, this.numberValue(value, name)]));
+            .map(([name, value]) => [name, this.attributeValue(value, name)]));
+    }
+    /**
+     * Read one property as the string the attribute of that name carries.
+     *
+     * Five of these properties are amounts and `RedrivePolicy` is a JSON
+     * document, so the two are read differently.
+     */
+    attributeValue(value, name) {
+        if (simSqsJsonQueueAttributeNames.has(name)) {
+            return this.documentValue(value, name);
+        }
+        return this.numberValue(value, name);
+    }
+    /**
+     * Read a JSON document property as the string an SQS attribute carries.
+     *
+     * CloudFormation carries the document as an object, and as a string when it
+     * came from a template Parameter or from a Terraform plan holding it as one.
+     * What the document has to say is left to SQS, which refuses a bad redrive
+     * policy in its own words.
+     */
+    documentValue(value, name) {
+        if (typeof value === "string") {
+            return value;
+        }
+        if (isRecord(value)) {
+            return jsonStringify(value);
+        }
+        throw this.propertyError(`${name} must be a JSON document`);
     }
     /**
      * Read a numeric property as the string an SQS attribute carries.

package/dist/service/sqs/cfn/queue/sim-cfn-sqs-queue-property-names.d.ts

@@ -1,10 +1,14 @@
+import type { SimCfnSkippedPropertyRules } from "../../../cloudformation/resource/ignore/sim-cfn-skipped-property.type.js";
 import type { SimCfnTemplateValue } from "../../../cloudformation/template/value/sim-cfn-template-value.js";
 /**
  * The AWS::SQS::Queue properties carrying a queue attribute of the same name.
  *
  * CloudFormation names these exactly as the SQS API names the attributes, so
  * they are handed to CreateQueue rather than applied here. That leaves the
- * ranges and defaults in one place: the ones simulated SQS already validates.
+ * ranges and defaults in one place, the ones simulated SQS already validates.
+ *
+ * Five of them are amounts. `RedrivePolicy` is a JSON document, and
+ * CloudFormation carries it as an object where SQS carries it as a string.
  */
 export declare const attributePropertyNames: ReadonlySet<string>;
 /**
@@ -12,12 +16,14 @@ export declare const attributePropertyNames: ReadonlySet<string>;
  * each of them would have changed.
  *
  * The queue is created without them and each one is recorded against the
- * Resource. A queue deployed without its redrive policy looks like a queue with
- * a dead-letter queue to the template that wrote it and has none, so a test
- * expecting a failed message to end up somewhere needs to find out that it
- * never will.
+ * Resource. A test reads the record to find out what the queue it deployed
+ * behaves differently to AWS about.
+ *
+ * A property whose value real SQS answers with a 400 states what it has to
+ * satisfy here as well. Nothing acts on the value either way, and reading it
+ * this far is what keeps a template AWS refuses from deploying.
  */
-export declare const unsimulatedPropertyReasons: ReadonlyMap<string, string>;
+export declare const unsimulatedPropertyReasons: SimCfnSkippedPropertyRules;
 /**
  * The FifoQueue values that ask for a FIFO queue. CloudFormation carries a
  * boolean property as either, depending on where the value came from.

package/dist/service/sqs/cfn/queue/sim-cfn-sqs-queue-property-names.js

@@ -1,15 +1,20 @@
+import { validateSimCfnSqsKmsDataKeyReusePeriod } from "./sim-cfn-sqs-queue-encryption-rules.js";
 /**
  * The AWS::SQS::Queue properties carrying a queue attribute of the same name.
  *
  * CloudFormation names these exactly as the SQS API names the attributes, so
  * they are handed to CreateQueue rather than applied here. That leaves the
- * ranges and defaults in one place: the ones simulated SQS already validates.
+ * ranges and defaults in one place, the ones simulated SQS already validates.
+ *
+ * Five of them are amounts. `RedrivePolicy` is a JSON document, and
+ * CloudFormation carries it as an object where SQS carries it as a string.
  */
 export const attributePropertyNames = new Set([
     "DelaySeconds",
     "MaximumMessageSize",
     "MessageRetentionPeriod",
     "ReceiveMessageWaitTimeSeconds",
+    "RedrivePolicy",
     "VisibilityTimeout",
 ]);
 /**
@@ -17,10 +22,12 @@ export const attributePropertyNames = new Set([
  * each of them would have changed.
  *
  * The queue is created without them and each one is recorded against the
- * Resource. A queue deployed without its redrive policy looks like a queue with
- * a dead-letter queue to the template that wrote it and has none, so a test
- * expecting a failed message to end up somewhere needs to find out that it
- * never will.
+ * Resource. A test reads the record to find out what the queue it deployed
+ * behaves differently to AWS about.
+ *
+ * A property whose value real SQS answers with a 400 states what it has to
+ * satisfy here as well. Nothing acts on the value either way, and reading it
+ * this far is what keeps a template AWS refuses from deploying.
  */
 export const unsimulatedPropertyReasons = new Map([
     ["ContentBasedDeduplication", "only standard queues are simulated"],
@@ -28,18 +35,16 @@ export const unsimulatedPropertyReasons = new Map([
     ["FifoThroughputLimit", "only standard queues are simulated"],
     [
         "KmsDataKeyReusePeriodSeconds",
-        "simulated SQS does not encrypt message bodies",
+        {
+            reason: "simulated SQS does not encrypt message bodies",
+            constraint: validateSimCfnSqsKmsDataKeyReusePeriod,
+        },
     ],
     ["KmsMasterKeyId", "simulated SQS does not encrypt message bodies"],
     [
         "RedriveAllowPolicy",
-        "dead-letter queues are not simulated, so nothing enforces which queues " +
-            "may name this one as theirs",
-    ],
-    [
-        "RedrivePolicy",
-        "dead-letter queues are not simulated, so a message that is received " +
-            "past maxReceiveCount stays on this queue rather than moving",
+        "nothing enforces which queues may name this one as their dead-letter " +
+            "queue, and setting the attribute through the SQS API is refused",
     ],
     ["SqsManagedSseEnabled", "simulated SQS does not encrypt message bodies"],
     ["Tags", "no simulated service reads a queue tag"],

package/dist/service/sqs/cfn/queue/sim-cfn-sqs-queue-property-rules.d.ts

@@ -27,6 +27,7 @@ export declare class SimCfnSqsQueuePropertyRules {
     private readonly logicalId;
     private readonly properties;
     private readonly ignorer;
+    private readonly skipped;
     constructor(properties: SimCfnSqsQueuePropertyRulesProperties);
     /**
      * Whether a property carries a queue attribute of the same name.

package/dist/service/sqs/cfn/queue/sim-cfn-sqs-queue-property-rules.js

@@ -1,3 +1,4 @@
+import { SimCfnSkippedProperties } from "../../../cloudformation/resource/ignore/sim-cfn-skipped-properties.js";
 import { attributePropertyNames, fifoQueueValues, standardQueueValues, unsimulatedPropertyReasons, } from "./sim-cfn-sqs-queue-property-names.js";
 /**
  * Build the error a property of an AWS::SQS::Queue Resource is refused with.
@@ -23,10 +24,16 @@ export class SimCfnSqsQueuePropertyRules {
     logicalId;
     properties;
     ignorer;
+    skipped;
     constructor(properties) {
         this.logicalId = properties.logicalId;
         this.properties = properties.properties;
         this.ignorer = properties.ignorer;
+        this.skipped = new SimCfnSkippedProperties({
+            rules: unsimulatedPropertyReasons,
+            properties: this.properties,
+            error: (reason) => sqsQueuePropertyError(this.logicalId, reason),
+        });
     }
     /**
      * Whether a property carries a queue attribute of the same name.
@@ -39,6 +46,7 @@ export class SimCfnSqsQueuePropertyRules {
      */
     apply() {
         this.applyToFifoQueue();
+        this.skipped.assertConstraints();
         for (const name of Object.keys(this.properties)) {
             this.applyToProperty(name);
         }
@@ -71,7 +79,7 @@ export class SimCfnSqsQueuePropertyRules {
         throw sqsQueuePropertyError(this.logicalId, "FifoQueue must be true or false");
     }
     applyToProperty(name) {
-        const unsimulatedReason = unsimulatedPropertyReasons.get(name);
+        const unsimulatedReason = this.skipped.reasonFor(name);
         if (unsimulatedReason !== undefined) {
             this.ignorer.ignoreProperty(name, `${name} is a real AWS::SQS::Queue property simulated SQS does not ` +
                 `act on: ${unsimulatedReason}`);

package/dist/terraform/map/sim-tf-map-sqs-redrive.d.ts

@@ -24,8 +24,9 @@ export declare function jsonDocument(context: TerraformMappingContext, key: stri
  *
  * Each names its queue in a `queue_url` attribute, which the queue resolves to
  * whether or not the URL itself was known at plan time. CloudFormation carries
- * both as properties of the `AWS::SQS::Queue`, and simulated SQS records each
- * one against the Resource: no message moves to a dead-letter queue here, and
- * nothing enforces which queues may name one as theirs.
+ * both as properties of the `AWS::SQS::Queue`. `RedrivePolicy` reaches
+ * CreateQueue from there and moves a message that has run out of receives.
+ * `RedriveAllowPolicy` is recorded against the Resource, since nothing
+ * enforces which queues may name this one as their dead-letter queue.
  */
 export declare const sqsRedriveFolds: ReadonlyMap<string, TerraformResourceFold>;

package/dist/terraform/map/sim-tf-map-sqs-redrive.js

@@ -40,9 +40,10 @@ export function jsonDocument(context, key) {
  *
  * Each names its queue in a `queue_url` attribute, which the queue resolves to
  * whether or not the URL itself was known at plan time. CloudFormation carries
- * both as properties of the `AWS::SQS::Queue`, and simulated SQS records each
- * one against the Resource: no message moves to a dead-letter queue here, and
- * nothing enforces which queues may name one as theirs.
+ * both as properties of the `AWS::SQS::Queue`. `RedrivePolicy` reaches
+ * CreateQueue from there and moves a message that has run out of receives.
+ * `RedriveAllowPolicy` is recorded against the Resource, since nothing
+ * enforces which queues may name this one as their dead-letter queue.
  */
 export const sqsRedriveFolds = new Map([
     [

package/docs/README.md

@@ -9,6 +9,7 @@ behaviour and includes example code that can be copied into tests or local devel
 - [API Gateway HTTP APIs](https://yulinsim.dev/services/apigatewayv2/ "Simulated API Gateway HTTP API usage docs")
 - [API Gateway REST APIs](https://yulinsim.dev/services/apigateway/ "Simulated API Gateway REST API usage docs")
 - [Athena](https://yulinsim.dev/services/athena/ "Simulated Amazon Athena usage docs")
+- [AWS Backup](https://yulinsim.dev/services/backup/ "Simulated AWS Backup usage docs")
 - [Bedrock](https://yulinsim.dev/services/bedrock/ "Simulated Amazon Bedrock usage docs")
 - [CloudFormation](https://yulinsim.dev/services/cloudformation/ "Simulated CloudFormation usage docs")
 - [CloudFront](https://yulinsim.dev/services/cloudfront/ "Simulated CloudFront usage docs")