@kensio/yulin 1.6.0 → 1.7.0

package/dist/service/cloudformation/stack/teardown/sim-cfn-stack-resource-batch-deleter.d.ts

@@ -0,0 +1,29 @@
+import type { SimAws } from "../../../aws/sim-aws.js";
+import type { SimCfnResource } from "../../resource/sim-cfn-resource.js";
+interface SimCfnStackResourceBatchDeleterProperties {
+    readonly simAws: SimAws;
+    readonly resources: ReadonlyMap<string, SimCfnResource>;
+}
+/**
+ * Deletes one batch of Stack Resources nothing still depends on.
+ *
+ * The caller guarantees that every supplied Resource is ready to delete. This
+ * class owns only the batch execution details: delete them in parallel, passing
+ * each the shared Stack context.
+ *
+ * It does not choose which Resources are ready, retry incomplete Resources, or
+ * update Stack lifecycle state.
+ */
+export declare class SimCfnStackResourceBatchDeleter {
+    private readonly simAws;
+    private readonly resources;
+    constructor(properties: SimCfnStackResourceBatchDeleterProperties);
+    /**
+     * Delete the supplied Resources concurrently.
+     *
+     * Each Resource still owns its own delete lifecycle and status transitions.
+     */
+    delete(resources: readonly SimCfnResource[]): Promise<void>;
+}
+export {};
+//# sourceMappingURL=sim-cfn-stack-resource-batch-deleter.d.ts.map

package/dist/service/cloudformation/stack/teardown/sim-cfn-stack-resource-batch-deleter.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"sim-cfn-stack-resource-batch-deleter.d.ts","sourceRoot":"","sources":["../../../../../src/service/cloudformation/stack/teardown/sim-cfn-stack-resource-batch-deleter.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,MAAM,EAAE,MAAM,yBAAyB,CAAC;AACtD,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,oCAAoC,CAAC;AAEzE,UAAU,yCAAyC;IACjD,QAAQ,CAAC,MAAM,EAAE,MAAM,CAAC;IACxB,QAAQ,CAAC,SAAS,EAAE,WAAW,CAAC,MAAM,EAAE,cAAc,CAAC,CAAC;CACzD;AAED;;;;;;;;;GASG;AACH,qBAAa,+BAA+B;IAC1C,OAAO,CAAC,QAAQ,CAAC,MAAM,CAAS;IAChC,OAAO,CAAC,QAAQ,CAAC,SAAS,CAAsC;IAEhE,YAAY,UAAU,EAAE,yCAAyC,EAGhE;IAED;;;;OAIG;IACG,MAAM,CAAC,SAAS,EAAE,SAAS,cAAc,EAAE,GAAG,OAAO,CAAC,IAAI,CAAC,CAShE;CACF"}

package/dist/service/cloudformation/stack/teardown/sim-cfn-stack-resource-batch-deleter.js

@@ -0,0 +1,32 @@
+/**
+ * Deletes one batch of Stack Resources nothing still depends on.
+ *
+ * The caller guarantees that every supplied Resource is ready to delete. This
+ * class owns only the batch execution details: delete them in parallel, passing
+ * each the shared Stack context.
+ *
+ * It does not choose which Resources are ready, retry incomplete Resources, or
+ * update Stack lifecycle state.
+ */
+export class SimCfnStackResourceBatchDeleter {
+    simAws;
+    resources;
+    constructor(properties) {
+        this.simAws = properties.simAws;
+        this.resources = properties.resources;
+    }
+    /**
+     * Delete the supplied Resources concurrently.
+     *
+     * Each Resource still owns its own delete lifecycle and status transitions.
+     */
+    async delete(resources) {
+        await Promise.all(resources.map(async (resource) => {
+            await resource.delete({
+                simAws: this.simAws,
+                resources: this.resources,
+            });
+        }));
+    }
+}
+//# sourceMappingURL=sim-cfn-stack-resource-batch-deleter.js.map

package/dist/service/cloudformation/stack/teardown/sim-cfn-stack-resource-batch-deleter.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"sim-cfn-stack-resource-batch-deleter.js","sourceRoot":"","sources":["../../../../../src/service/cloudformation/stack/teardown/sim-cfn-stack-resource-batch-deleter.ts"],"names":[],"mappings":"AAQA;;;;;;;;;GASG;AACH,MAAM,OAAO,+BAA+B;IACzB,MAAM,CAAS;IACf,SAAS,CAAsC;IAEhE,YAAY,UAAqD;QAC/D,IAAI,CAAC,MAAM,GAAG,UAAU,CAAC,MAAM,CAAC;QAChC,IAAI,CAAC,SAAS,GAAG,UAAU,CAAC,SAAS,CAAC;IACxC,CAAC;IAED;;;;OAIG;IACH,KAAK,CAAC,MAAM,CAAC,SAAoC;QAC/C,MAAM,OAAO,CAAC,GAAG,CACf,SAAS,CAAC,GAAG,CAAC,KAAK,EAAE,QAAQ,EAAE,EAAE;YAC/B,MAAM,QAAQ,CAAC,MAAM,CAAC;gBACpB,MAAM,EAAE,IAAI,CAAC,MAAM;gBACnB,SAAS,EAAE,IAAI,CAAC,SAAS;aAC1B,CAAC,CAAC;QACL,CAAC,CAAC,CACH,CAAC;IACJ,CAAC;CACF"}

package/dist/service/cloudformation/stack/teardown/sim-cfn-stack-resource-deleter.d.ts

@@ -0,0 +1,52 @@
+import type { SimAws } from "../../../aws/sim-aws.js";
+import type { SimCfnResource } from "../../resource/sim-cfn-resource.js";
+interface SimCfnStackResourceDeleterProperties {
+    readonly simAws: SimAws;
+    readonly resources: ReadonlyMap<string, SimCfnResource>;
+    readonly stackName: string;
+}
+/**
+ * Orchestrates reverse-dependency-ordered deletion of a Stack's Resources.
+ *
+ * The mirror image of SimCfnStackResourceCreator:
+ *
+ * - ask SimCfnStackPendingDeletions which pending Resources nothing depends on
+ * - fail if no pending Resource can make progress
+ * - ask SimCfnStackResourceBatchDeleter to delete the ready batch
+ * - repeat with the Resources that are still not delete-complete
+ *
+ * Deleting in this order is what makes the individual service deleters
+ * workable: a Bucket policy is gone before its Bucket, a Role's policies before
+ * the Role, and every Ref a Resource carries still resolves while that Resource
+ * is being deleted.
+ */
+export declare class SimCfnStackResourceDeleter {
+    private readonly resources;
+    private readonly stackName;
+    private readonly batchDeleter;
+    constructor(properties: SimCfnStackResourceDeleterProperties);
+    /**
+     * Delete every Stack Resource once nothing depends on it any more.
+     *
+     * What a teardown does, where an update deletes only the Resources its
+     * template dropped or replaced.
+     */
+    deleteAll(): Promise<void>;
+    /**
+     * Delete the given Stack Resources once nothing depends on them any more.
+     *
+     * The loop is sequential between batches because a Resource can only go once
+     * the Resources naming it have gone. Deletion inside a batch is parallel and
+     * delegated to SimCfnStackResourceBatchDeleter.
+     *
+     * Dependents are read across every Resource in the Stack rather than only the
+     * ones being deleted, so a Resource an update leaves alone still holds up the
+     * Resource it names.
+     *
+     * If a loop iteration finds pending Resources but none are deletable, the
+     * template's dependencies are cyclic, the same condition creation reports.
+     */
+    delete(deleting: readonly SimCfnResource[]): Promise<void>;
+}
+export {};
+//# sourceMappingURL=sim-cfn-stack-resource-deleter.d.ts.map

package/dist/service/cloudformation/stack/teardown/sim-cfn-stack-resource-deleter.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"sim-cfn-stack-resource-deleter.d.ts","sourceRoot":"","sources":["../../../../../src/service/cloudformation/stack/teardown/sim-cfn-stack-resource-deleter.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,MAAM,EAAE,MAAM,yBAAyB,CAAC;AACtD,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,oCAAoC,CAAC;AAIzE,UAAU,oCAAoC;IAC5C,QAAQ,CAAC,MAAM,EAAE,MAAM,CAAC;IACxB,QAAQ,CAAC,SAAS,EAAE,WAAW,CAAC,MAAM,EAAE,cAAc,CAAC,CAAC;IACxD,QAAQ,CAAC,SAAS,EAAE,MAAM,CAAC;CAC5B;AAED;;;;;;;;;;;;;;GAcG;AACH,qBAAa,0BAA0B;IACrC,OAAO,CAAC,QAAQ,CAAC,SAAS,CAAsC;IAChE,OAAO,CAAC,QAAQ,CAAC,SAAS,CAAS;IACnC,OAAO,CAAC,QAAQ,CAAC,YAAY,CAAkC;IAE/D,YAAY,UAAU,EAAE,oCAAoC,EAS3D;IAED;;;;;OAKG;IACG,SAAS,IAAI,OAAO,CAAC,IAAI,CAAC,CAE/B;IAED;;;;;;;;;;;;;OAaG;IACG,MAAM,CAAC,QAAQ,EAAE,SAAS,cAAc,EAAE,GAAG,OAAO,CAAC,IAAI,CAAC,CAoB/D;CACF"}

package/dist/service/cloudformation/stack/teardown/sim-cfn-stack-resource-deleter.js

@@ -0,0 +1,67 @@
+import { SimCfnStackPendingDeletions } from "./sim-cfn-stack-pending-deletions.js";
+import { SimCfnStackResourceBatchDeleter } from "./sim-cfn-stack-resource-batch-deleter.js";
+/**
+ * Orchestrates reverse-dependency-ordered deletion of a Stack's Resources.
+ *
+ * The mirror image of SimCfnStackResourceCreator:
+ *
+ * - ask SimCfnStackPendingDeletions which pending Resources nothing depends on
+ * - fail if no pending Resource can make progress
+ * - ask SimCfnStackResourceBatchDeleter to delete the ready batch
+ * - repeat with the Resources that are still not delete-complete
+ *
+ * Deleting in this order is what makes the individual service deleters
+ * workable: a Bucket policy is gone before its Bucket, a Role's policies before
+ * the Role, and every Ref a Resource carries still resolves while that Resource
+ * is being deleted.
+ */
+export class SimCfnStackResourceDeleter {
+    resources;
+    stackName;
+    batchDeleter;
+    constructor(properties) {
+        const { simAws, resources, stackName } = properties;
+        this.resources = resources;
+        this.stackName = stackName;
+        this.batchDeleter = new SimCfnStackResourceBatchDeleter({
+            simAws,
+            resources,
+        });
+    }
+    /**
+     * Delete every Stack Resource once nothing depends on it any more.
+     *
+     * What a teardown does, where an update deletes only the Resources its
+     * template dropped or replaced.
+     */
+    async deleteAll() {
+        await this.delete(this.resources.values().toArray());
+    }
+    /**
+     * Delete the given Stack Resources once nothing depends on them any more.
+     *
+     * The loop is sequential between batches because a Resource can only go once
+     * the Resources naming it have gone. Deletion inside a batch is parallel and
+     * delegated to SimCfnStackResourceBatchDeleter.
+     *
+     * Dependents are read across every Resource in the Stack rather than only the
+     * ones being deleted, so a Resource an update leaves alone still holds up the
+     * Resource it names.
+     *
+     * If a loop iteration finds pending Resources but none are deletable, the
+     * template's dependencies are cyclic, the same condition creation reports.
+     */
+    async delete(deleting) {
+        let pendingDeletions = new SimCfnStackPendingDeletions(this.resources, new Set(deleting));
+        while (pendingDeletions.hasResources) {
+            const deletableResources = pendingDeletions.deletableResources();
+            if (deletableResources.length === 0) {
+                throw new Error(`Could not resolve simulated CloudFormation Resource dependencies to delete Stack ${this.stackName}`);
+            }
+            // eslint-disable-next-line no-await-in-loop
+            await this.batchDeleter.delete(deletableResources);
+            pendingDeletions = pendingDeletions.incompleteResources();
+        }
+    }
+}
+//# sourceMappingURL=sim-cfn-stack-resource-deleter.js.map

package/dist/service/cloudformation/stack/teardown/sim-cfn-stack-resource-deleter.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"sim-cfn-stack-resource-deleter.js","sourceRoot":"","sources":["../../../../../src/service/cloudformation/stack/teardown/sim-cfn-stack-resource-deleter.ts"],"names":[],"mappings":"AAEA,OAAO,EAAE,2BAA2B,EAAE,MAAM,sCAAsC,CAAC;AACnF,OAAO,EAAE,+BAA+B,EAAE,MAAM,2CAA2C,CAAC;AAQ5F;;;;;;;;;;;;;;GAcG;AACH,MAAM,OAAO,0BAA0B;IACpB,SAAS,CAAsC;IAC/C,SAAS,CAAS;IAClB,YAAY,CAAkC;IAE/D,YAAY,UAAgD;QAC1D,MAAM,EAAE,MAAM,EAAE,SAAS,EAAE,SAAS,EAAE,GAAG,UAAU,CAAC;QAEpD,IAAI,CAAC,SAAS,GAAG,SAAS,CAAC;QAC3B,IAAI,CAAC,SAAS,GAAG,SAAS,CAAC;QAC3B,IAAI,CAAC,YAAY,GAAG,IAAI,+BAA+B,CAAC;YACtD,MAAM;YACN,SAAS;SACV,CAAC,CAAC;IACL,CAAC;IAED;;;;;OAKG;IACH,KAAK,CAAC,SAAS;QACb,MAAM,IAAI,CAAC,MAAM,CAAC,IAAI,CAAC,SAAS,CAAC,MAAM,EAAE,CAAC,OAAO,EAAE,CAAC,CAAC;IACvD,CAAC;IAED;;;;;;;;;;;;;OAaG;IACH,KAAK,CAAC,MAAM,CAAC,QAAmC;QAC9C,IAAI,gBAAgB,GAAG,IAAI,2BAA2B,CACpD,IAAI,CAAC,SAAS,EACd,IAAI,GAAG,CAAC,QAAQ,CAAC,CAClB,CAAC;QAEF,OAAO,gBAAgB,CAAC,YAAY,EAAE,CAAC;YACrC,MAAM,kBAAkB,GAAG,gBAAgB,CAAC,kBAAkB,EAAE,CAAC;YAEjE,IAAI,kBAAkB,CAAC,MAAM,KAAK,CAAC,EAAE,CAAC;gBACpC,MAAM,IAAI,KAAK,CACb,oFAAoF,IAAI,CAAC,SAAS,EAAE,CACrG,CAAC;YACJ,CAAC;YAED,4CAA4C;YAC5C,MAAM,IAAI,CAAC,YAAY,CAAC,MAAM,CAAC,kBAAkB,CAAC,CAAC;YAEnD,gBAAgB,GAAG,gBAAgB,CAAC,mBAAmB,EAAE,CAAC;QAC5D,CAAC;IACH,CAAC;CACF"}

package/dist/service/cloudformation/stack/update/sim-cfn-stack-replaced-resources.d.ts

@@ -0,0 +1,22 @@
+import type { SimCfnResource } from "../../resource/sim-cfn-resource.js";
+interface SimCfnStackReplacedResourcesProperties {
+    readonly current: ReadonlyMap<string, SimCfnResource>;
+    readonly updated: ReadonlyMap<string, SimCfnResource>;
+}
+/**
+ * The logical IDs an update has to replace, given the Stack's deployed
+ * Resources and the ones its new template describes.
+ *
+ * A Resource is replaced when its resolved template entry changed. Sim
+ * CloudFormation has no in-place update, so replacement means deleting the
+ * Resource and creating it again from the new template.
+ *
+ * A Resource that names a replaced Resource is replaced too, all the way up the
+ * dependency chain. Real CloudFormation hands the dependent the new physical
+ * name instead, but nothing here can rewrite an already created simulated
+ * Resource, and leaving the dependent alone would leave it pointing at a
+ * Resource that has gone.
+ */
+export declare function simCfnStackReplacedLogicalIds(properties: SimCfnStackReplacedResourcesProperties): ReadonlySet<string>;
+export {};
+//# sourceMappingURL=sim-cfn-stack-replaced-resources.d.ts.map

package/dist/service/cloudformation/stack/update/sim-cfn-stack-replaced-resources.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"sim-cfn-stack-replaced-resources.d.ts","sourceRoot":"","sources":["../../../../../src/service/cloudformation/stack/update/sim-cfn-stack-replaced-resources.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,oCAAoC,CAAC;AAGzE,UAAU,sCAAsC;IAC9C,QAAQ,CAAC,OAAO,EAAE,WAAW,CAAC,MAAM,EAAE,cAAc,CAAC,CAAC;IACtD,QAAQ,CAAC,OAAO,EAAE,WAAW,CAAC,MAAM,EAAE,cAAc,CAAC,CAAC;CACvD;AAED;;;;;;;;;;;;;GAaG;AACH,wBAAgB,6BAA6B,CAC3C,UAAU,EAAE,sCAAsC,GACjD,WAAW,CAAC,MAAM,CAAC,CAyBrB"}

package/dist/service/cloudformation/stack/update/sim-cfn-stack-replaced-resources.js

@@ -0,0 +1,52 @@
+import { simCfnTemplateSignature } from "./sim-cfn-template-signature.js";
+/**
+ * The logical IDs an update has to replace, given the Stack's deployed
+ * Resources and the ones its new template describes.
+ *
+ * A Resource is replaced when its resolved template entry changed. Sim
+ * CloudFormation has no in-place update, so replacement means deleting the
+ * Resource and creating it again from the new template.
+ *
+ * A Resource that names a replaced Resource is replaced too, all the way up the
+ * dependency chain. Real CloudFormation hands the dependent the new physical
+ * name instead, but nothing here can rewrite an already created simulated
+ * Resource, and leaving the dependent alone would leave it pointing at a
+ * Resource that has gone.
+ */
+export function simCfnStackReplacedLogicalIds(properties) {
+    const { current, updated } = properties;
+    const replaced = changedLogicalIds({ current, updated });
+    // Each pass replaces the Resources naming one already being replaced, until a
+    // pass finds none, which is the end of the dependency chain.
+    let spreading = true;
+    while (spreading) {
+        spreading = false;
+        for (const [logicalId, resource] of updated) {
+            const spreads = current.has(logicalId) &&
+                !replaced.has(logicalId) &&
+                resource.dependencies().some((dependency) => replaced.has(dependency));
+            if (spreads) {
+                replaced.add(logicalId);
+                spreading = true;
+            }
+        }
+    }
+    return replaced;
+}
+/**
+ * The logical IDs whose resolved template entry differs from the deployed one.
+ */
+function changedLogicalIds(properties) {
+    const { current, updated } = properties;
+    const changed = new Set();
+    for (const [logicalId, resource] of updated) {
+        const deployed = current.get(logicalId);
+        if (deployed !== undefined &&
+            simCfnTemplateSignature(deployed.template) !==
+                simCfnTemplateSignature(resource.template)) {
+            changed.add(logicalId);
+        }
+    }
+    return changed;
+}
+//# sourceMappingURL=sim-cfn-stack-replaced-resources.js.map

package/dist/service/cloudformation/stack/update/sim-cfn-stack-replaced-resources.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"sim-cfn-stack-replaced-resources.js","sourceRoot":"","sources":["../../../../../src/service/cloudformation/stack/update/sim-cfn-stack-replaced-resources.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,uBAAuB,EAAE,MAAM,iCAAiC,CAAC;AAO1E;;;;;;;;;;;;;GAaG;AACH,MAAM,UAAU,6BAA6B,CAC3C,UAAkD;IAElD,MAAM,EAAE,OAAO,EAAE,OAAO,EAAE,GAAG,UAAU,CAAC;IACxC,MAAM,QAAQ,GAAG,iBAAiB,CAAC,EAAE,OAAO,EAAE,OAAO,EAAE,CAAC,CAAC;IAEzD,8EAA8E;IAC9E,6DAA6D;IAC7D,IAAI,SAAS,GAAG,IAAI,CAAC;IAErB,OAAO,SAAS,EAAE,CAAC;QACjB,SAAS,GAAG,KAAK,CAAC;QAElB,KAAK,MAAM,CAAC,SAAS,EAAE,QAAQ,CAAC,IAAI,OAAO,EAAE,CAAC;YAC5C,MAAM,OAAO,GACX,OAAO,CAAC,GAAG,CAAC,SAAS,CAAC;gBACtB,CAAC,QAAQ,CAAC,GAAG,CAAC,SAAS,CAAC;gBACxB,QAAQ,CAAC,YAAY,EAAE,CAAC,IAAI,CAAC,CAAC,UAAU,EAAE,EAAE,CAAC,QAAQ,CAAC,GAAG,CAAC,UAAU,CAAC,CAAC,CAAC;YAEzE,IAAI,OAAO,EAAE,CAAC;gBACZ,QAAQ,CAAC,GAAG,CAAC,SAAS,CAAC,CAAC;gBACxB,SAAS,GAAG,IAAI,CAAC;YACnB,CAAC;QACH,CAAC;IACH,CAAC;IAED,OAAO,QAAQ,CAAC;AAClB,CAAC;AAED;;GAEG;AACH,SAAS,iBAAiB,CACxB,UAAkD;IAElD,MAAM,EAAE,OAAO,EAAE,OAAO,EAAE,GAAG,UAAU,CAAC;IACxC,MAAM,OAAO,GAAG,IAAI,GAAG,EAAU,CAAC;IAElC,KAAK,MAAM,CAAC,SAAS,EAAE,QAAQ,CAAC,IAAI,OAAO,EAAE,CAAC;QAC5C,MAAM,QAAQ,GAAG,OAAO,CAAC,GAAG,CAAC,SAAS,CAAC,CAAC;QAExC,IACE,QAAQ,KAAK,SAAS;YACtB,uBAAuB,CAAC,QAAQ,CAAC,QAAQ,CAAC;gBACxC,uBAAuB,CAAC,QAAQ,CAAC,QAAQ,CAAC,EAC5C,CAAC;YACD,OAAO,CAAC,GAAG,CAAC,SAAS,CAAC,CAAC;QACzB,CAAC;IACH,CAAC;IAED,OAAO,OAAO,CAAC;AACjB,CAAC"}

package/dist/service/cloudformation/stack/update/sim-cfn-stack-template-changes.d.ts

@@ -0,0 +1,16 @@
+import type { SimCfnTemplate } from "../../template/sim-cfn-template.js";
+/**
+ * Whether a new template says anything different from the deployed one, apart
+ * from its Resources.
+ *
+ * An update that changes nothing but an Output, a Description, or a section
+ * this simulation does not read is still an update, so the whole template body
+ * is compared alongside the Resource half of the difference.
+ *
+ * The body alone is not enough, because a Parameter given a new value changes
+ * what the template means without changing a character of it. The Outputs are
+ * therefore also compared as they resolve, which is where such a change shows
+ * through. SimCfnStackUpdatePlan compares the Resources the same way.
+ */
+export declare function simCfnStackTemplateChanged(current: SimCfnTemplate, updated: SimCfnTemplate): boolean;
+//# sourceMappingURL=sim-cfn-stack-template-changes.d.ts.map

package/dist/service/cloudformation/stack/update/sim-cfn-stack-template-changes.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"sim-cfn-stack-template-changes.d.ts","sourceRoot":"","sources":["../../../../../src/service/cloudformation/stack/update/sim-cfn-stack-template-changes.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,oCAAoC,CAAC;AAIzE;;;;;;;;;;;;GAYG;AACH,wBAAgB,0BAA0B,CACxC,OAAO,EAAE,cAAc,EACvB,OAAO,EAAE,cAAc,GACtB,OAAO,CAOT"}

package/dist/service/cloudformation/stack/update/sim-cfn-stack-template-changes.js

@@ -0,0 +1,32 @@
+import { simCfnTemplateSignature } from "./sim-cfn-template-signature.js";
+/**
+ * Whether a new template says anything different from the deployed one, apart
+ * from its Resources.
+ *
+ * An update that changes nothing but an Output, a Description, or a section
+ * this simulation does not read is still an update, so the whole template body
+ * is compared alongside the Resource half of the difference.
+ *
+ * The body alone is not enough, because a Parameter given a new value changes
+ * what the template means without changing a character of it. The Outputs are
+ * therefore also compared as they resolve, which is where such a change shows
+ * through. SimCfnStackUpdatePlan compares the Resources the same way.
+ */
+export function simCfnStackTemplateChanged(current, updated) {
+    return (simCfnTemplateSignature(current.template) !==
+        simCfnTemplateSignature(updated.template) ||
+        simCfnTemplateSignature(outputRecord(current)) !==
+            simCfnTemplateSignature(outputRecord(updated)));
+}
+/**
+ * A template's Output entries in one record, for the signature to be taken of.
+ */
+function outputRecord(template) {
+    return Object.fromEntries(template
+        .outputTemplates()
+        .map((outputTemplate) => [
+        outputTemplate.outputKey,
+        outputTemplate.template,
+    ]));
+}
+//# sourceMappingURL=sim-cfn-stack-template-changes.js.map

package/dist/service/cloudformation/stack/update/sim-cfn-stack-template-changes.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"sim-cfn-stack-template-changes.js","sourceRoot":"","sources":["../../../../../src/service/cloudformation/stack/update/sim-cfn-stack-template-changes.ts"],"names":[],"mappings":"AAEA,OAAO,EAAE,uBAAuB,EAAE,MAAM,iCAAiC,CAAC;AAE1E;;;;;;;;;;;;GAYG;AACH,MAAM,UAAU,0BAA0B,CACxC,OAAuB,EACvB,OAAuB;IAEvB,OAAO,CACL,uBAAuB,CAAC,OAAO,CAAC,QAAQ,CAAC;QACvC,uBAAuB,CAAC,OAAO,CAAC,QAAQ,CAAC;QAC3C,uBAAuB,CAAC,YAAY,CAAC,OAAO,CAAC,CAAC;YAC5C,uBAAuB,CAAC,YAAY,CAAC,OAAO,CAAC,CAAC,CACjD,CAAC;AACJ,CAAC;AAED;;GAEG;AACH,SAAS,YAAY,CAAC,QAAwB;IAC5C,OAAO,MAAM,CAAC,WAAW,CACvB,QAAQ;SACL,eAAe,EAAE;SACjB,GAAG,CAAC,CAAC,cAAc,EAAE,EAAE,CAAC;QACvB,cAAc,CAAC,SAAS;QACxB,cAAc,CAAC,QAAQ;KACxB,CAAC,CACL,CAAC;AACJ,CAAC"}

package/dist/service/cloudformation/stack/update/sim-cfn-stack-update-lifecycle.d.ts

@@ -0,0 +1,64 @@
+import type { BackgroundScheduler } from "../../../../util/background/background.js";
+import type { SimCloudFormationStackName, SimCloudFormationStackStatus } from "../sim-cfn-stack.js";
+interface SimCfnStackUpdateLifecycleProperties {
+    readonly background: BackgroundScheduler;
+    readonly stackName: SimCloudFormationStackName;
+}
+/**
+ * Owns the simulated CloudFormation Stack update lifecycle state.
+ *
+ * The third of the Stack operation lifecycles, alongside
+ * SimCfnStackDeploymentLifecycle and SimCfnStackDeletionLifecycle, and separate
+ * from both for the same reason they are separate from each other: a Stack that
+ * was never updated has no update status at all, and its deployment status is
+ * still the thing to report.
+ *
+ * The work itself is passed in per update, because each one applies a different
+ * template. This class only says what the Stack is doing and what went wrong.
+ */
+export declare class SimCfnStackUpdateLifecycle {
+    #private;
+    private readonly background;
+    private readonly stackName;
+    private completePromise;
+    private updateError;
+    constructor(properties: SimCfnStackUpdateLifecycleProperties);
+    /**
+     * The current Stack update status, or undefined if the Stack has never been
+     * updated.
+     */
+    get status(): SimCloudFormationStackStatus | undefined;
+    /**
+     * The error captured during a background update, if any.
+     */
+    get error(): Error | undefined;
+    /**
+     * Refuse an update while one is already running.
+     *
+     * CloudFormation takes one update at a time, and a second here would read
+     * the difference to apply from a Stack half way through the first.
+     */
+    assertNotUpdating(): void;
+    /**
+     * Start the Stack update lifecycle.
+     *
+     * The returned promise only covers sequencing and scheduling, as deployment
+     * and deletion do. The Resource work continues in the background, so callers
+     * that need the final state should use waitForComplete().
+     *
+     * An update that fails leaves the Stack in UPDATE_FAILED with the reason on
+     * it. Sim CloudFormation does not roll the Stack back to the template it was
+     * deployed from, so the Stack is left holding whatever the update managed.
+     */
+    update(runUpdate: () => Promise<void>): Promise<void>;
+    /**
+     * Wait for the scheduled update to finish.
+     *
+     * If the update failed, this rethrows the captured error, so a caller can see
+     * what stopped the new template being applied. A Stack that was never updated
+     * has nothing to wait for.
+     */
+    waitForComplete(): Promise<void>;
+}
+export {};
+//# sourceMappingURL=sim-cfn-stack-update-lifecycle.d.ts.map

package/dist/service/cloudformation/stack/update/sim-cfn-stack-update-lifecycle.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"sim-cfn-stack-update-lifecycle.d.ts","sourceRoot":"","sources":["../../../../../src/service/cloudformation/stack/update/sim-cfn-stack-update-lifecycle.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,mBAAmB,EAAE,MAAM,2CAA2C,CAAC;AAErF,OAAO,KAAK,EACV,0BAA0B,EAC1B,4BAA4B,EAC7B,MAAM,qBAAqB,CAAC;AAG7B,UAAU,oCAAoC;IAC5C,QAAQ,CAAC,UAAU,EAAE,mBAAmB,CAAC;IACzC,QAAQ,CAAC,SAAS,EAAE,0BAA0B,CAAC;CAChD;AAED;;;;;;;;;;;GAWG;AACH,qBAAa,0BAA0B;;IACrC,OAAO,CAAC,QAAQ,CAAC,UAAU,CAAsB;IACjD,OAAO,CAAC,QAAQ,CAAC,SAAS,CAA6B;IAGvD,OAAO,CAAC,eAAe,CAA4B;IACnD,OAAO,CAAC,WAAW,CAAoB;IAEvC,YAAY,UAAU,EAAE,oCAAoC,EAG3D;IAED;;;OAGG;IACH,IAAW,MAAM,IAAI,4BAA4B,GAAG,SAAS,CAE5D;IAED;;OAEG;IACH,IAAW,KAAK,IAAI,KAAK,GAAG,SAAS,CAEpC;IAED;;;;;OAKG;IACH,iBAAiB,IAAI,IAAI,CAMxB;IAED;;;;;;;;;;OAUG;IACU,MAAM,CAAC,SAAS,EAAE,MAAM,OAAO,CAAC,IAAI,CAAC,GAAG,OAAO,CAAC,IAAI,CAAC,CAqBjE;IAED;;;;;;OAMG;IACU,eAAe,IAAI,OAAO,CAAC,IAAI,CAAC,CAQ5C;CACF"}

package/dist/service/cloudformation/stack/update/sim-cfn-stack-update-lifecycle.js

@@ -0,0 +1,95 @@
+import { SimCloudFormationValidationError } from "../../error/sim-cloudformation.error.js";
+import { SimCfnStackOperationScheduler } from "../sim-cfn-stack-operation-scheduler.js";
+/**
+ * Owns the simulated CloudFormation Stack update lifecycle state.
+ *
+ * The third of the Stack operation lifecycles, alongside
+ * SimCfnStackDeploymentLifecycle and SimCfnStackDeletionLifecycle, and separate
+ * from both for the same reason they are separate from each other: a Stack that
+ * was never updated has no update status at all, and its deployment status is
+ * still the thing to report.
+ *
+ * The work itself is passed in per update, because each one applies a different
+ * template. This class only says what the Stack is doing and what went wrong.
+ */
+export class SimCfnStackUpdateLifecycle {
+    background;
+    stackName;
+    #status;
+    completePromise;
+    updateError;
+    constructor(properties) {
+        this.background = properties.background;
+        this.stackName = properties.stackName;
+    }
+    /**
+     * The current Stack update status, or undefined if the Stack has never been
+     * updated.
+     */
+    get status() {
+        return this.#status;
+    }
+    /**
+     * The error captured during a background update, if any.
+     */
+    get error() {
+        return this.updateError;
+    }
+    /**
+     * Refuse an update while one is already running.
+     *
+     * CloudFormation takes one update at a time, and a second here would read
+     * the difference to apply from a Stack half way through the first.
+     */
+    assertNotUpdating() {
+        if (this.#status === "UPDATE_IN_PROGRESS") {
+            throw new SimCloudFormationValidationError(`Stack ${this.stackName} is in UPDATE_IN_PROGRESS state and can not be updated`);
+        }
+    }
+    /**
+     * Start the Stack update lifecycle.
+     *
+     * The returned promise only covers sequencing and scheduling, as deployment
+     * and deletion do. The Resource work continues in the background, so callers
+     * that need the final state should use waitForComplete().
+     *
+     * An update that fails leaves the Stack in UPDATE_FAILED with the reason on
+     * it. Sim CloudFormation does not roll the Stack back to the template it was
+     * deployed from, so the Stack is left holding whatever the update managed.
+     */
+    async update(runUpdate) {
+        this.#status = "UPDATE_IN_PROGRESS";
+        this.updateError = undefined;
+        const scheduler = new SimCfnStackOperationScheduler({
+            background: this.background,
+            failureMessage: "Sim CloudFormation Stack update failed",
+        });
+        await scheduler.sequence();
+        this.completePromise = scheduler.schedule({
+            operation: runUpdate,
+            onSuccess: () => {
+                this.#status = "UPDATE_COMPLETE";
+            },
+            onFailure: (error) => {
+                this.#status = "UPDATE_FAILED";
+                this.updateError = error;
+            },
+        });
+    }
+    /**
+     * Wait for the scheduled update to finish.
+     *
+     * If the update failed, this rethrows the captured error, so a caller can see
+     * what stopped the new template being applied. A Stack that was never updated
+     * has nothing to wait for.
+     */
+    async waitForComplete() {
+        if (this.completePromise !== undefined) {
+            await this.completePromise;
+        }
+        if (this.updateError !== undefined) {
+            throw this.updateError;
+        }
+    }
+}
+//# sourceMappingURL=sim-cfn-stack-update-lifecycle.js.map

package/dist/service/cloudformation/stack/update/sim-cfn-stack-update-lifecycle.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"sim-cfn-stack-update-lifecycle.js","sourceRoot":"","sources":["../../../../../src/service/cloudformation/stack/update/sim-cfn-stack-update-lifecycle.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,gCAAgC,EAAE,MAAM,yCAAyC,CAAC;AAK3F,OAAO,EAAE,6BAA6B,EAAE,MAAM,yCAAyC,CAAC;AAOxF;;;;;;;;;;;GAWG;AACH,MAAM,OAAO,0BAA0B;IACpB,UAAU,CAAsB;IAChC,SAAS,CAA6B;IACvD,OAAO,CAA2C;IAE1C,eAAe,CAA4B;IAC3C,WAAW,CAAoB;IAEvC,YAAY,UAAgD;QAC1D,IAAI,CAAC,UAAU,GAAG,UAAU,CAAC,UAAU,CAAC;QACxC,IAAI,CAAC,SAAS,GAAG,UAAU,CAAC,SAAS,CAAC;IACxC,CAAC;IAED;;;OAGG;IACH,IAAW,MAAM;QACf,OAAO,IAAI,CAAC,OAAO,CAAC;IACtB,CAAC;IAED;;OAEG;IACH,IAAW,KAAK;QACd,OAAO,IAAI,CAAC,WAAW,CAAC;IAC1B,CAAC;IAED;;;;;OAKG;IACH,iBAAiB;QACf,IAAI,IAAI,CAAC,OAAO,KAAK,oBAAoB,EAAE,CAAC;YAC1C,MAAM,IAAI,gCAAgC,CACxC,SAAS,IAAI,CAAC,SAAS,wDAAwD,CAChF,CAAC;QACJ,CAAC;IACH,CAAC;IAED;;;;;;;;;;OAUG;IACI,KAAK,CAAC,MAAM,CAAC,SAA8B;QAChD,IAAI,CAAC,OAAO,GAAG,oBAAoB,CAAC;QACpC,IAAI,CAAC,WAAW,GAAG,SAAS,CAAC;QAE7B,MAAM,SAAS,GAAG,IAAI,6BAA6B,CAAC;YAClD,UAAU,EAAE,IAAI,CAAC,UAAU;YAC3B,cAAc,EAAE,wCAAwC;SACzD,CAAC,CAAC;QAEH,MAAM,SAAS,CAAC,QAAQ,EAAE,CAAC;QAE3B,IAAI,CAAC,eAAe,GAAG,SAAS,CAAC,QAAQ,CAAC;YACxC,SAAS,EAAE,SAAS;YACpB,SAAS,EAAE,GAAG,EAAE;gBACd,IAAI,CAAC,OAAO,GAAG,iBAAiB,CAAC;YACnC,CAAC;YACD,SAAS,EAAE,CAAC,KAAK,EAAE,EAAE;gBACnB,IAAI,CAAC,OAAO,GAAG,eAAe,CAAC;gBAC/B,IAAI,CAAC,WAAW,GAAG,KAAK,CAAC;YAC3B,CAAC;SACF,CAAC,CAAC;IACL,CAAC;IAED;;;;;;OAMG;IACI,KAAK,CAAC,eAAe;QAC1B,IAAI,IAAI,CAAC,eAAe,KAAK,SAAS,EAAE,CAAC;YACvC,MAAM,IAAI,CAAC,eAAe,CAAC;QAC7B,CAAC;QAED,IAAI,IAAI,CAAC,WAAW,KAAK,SAAS,EAAE,CAAC;YACnC,MAAM,IAAI,CAAC,WAAW,CAAC;QACzB,CAAC;IACH,CAAC;CACF"}

package/dist/service/cloudformation/stack/update/sim-cfn-stack-update-plan.d.ts

@@ -0,0 +1,50 @@
+import type { SimCfnResource } from "../../resource/sim-cfn-resource.js";
+interface SimCfnStackUpdatePlanProperties {
+    readonly current: ReadonlyMap<string, SimCfnResource>;
+    readonly updated: ReadonlyMap<string, SimCfnResource>;
+}
+/**
+ * What an update has to do to a Stack's Resources, worked out before any of it
+ * happens.
+ *
+ * The plan compares the Resources the Stack has with the ones its new template
+ * describes, and says which to delete, which to create, and what the Stack
+ * holds afterwards. A Resource the template still describes unchanged is left
+ * alone, keeping whatever it holds in simulated AWS.
+ *
+ * It does not delete or create anything, order the work, or decide what counts
+ * as a changed Resource. SimCfnStackUpdater runs the plan, and
+ * simCfnStackReplacedLogicalIds decides what changed.
+ */
+export declare class SimCfnStackUpdatePlan {
+    /**
+     * The deployed Resources to delete: the ones the new template drops, and the
+     * deployed halves of the ones it replaces.
+     */
+    readonly deletions: readonly SimCfnResource[];
+    /**
+     * The new Resources to create: the ones the new template adds, and the new
+     * halves of the ones it replaces.
+     */
+    readonly creations: readonly SimCfnResource[];
+    private readonly updated;
+    constructor(properties: SimCfnStackUpdatePlanProperties);
+    /**
+     * Whether the update changes any Resource at all.
+     *
+     * A template that only changes something else, such as an Output, still
+     * updates the Stack, so this is not the whole no-op question.
+     */
+    get changesResources(): boolean;
+    /**
+     * Move the Stack's Resource map on to the new template.
+     *
+     * The map is changed in place rather than replaced, so anything already
+     * holding the Stack's Resources sees the update. A Resource the template
+     * leaves alone keeps the object it already had, which is what keeps its
+     * simulated AWS Resource and its creation status.
+     */
+    applyTo(resources: Map<string, SimCfnResource>): void;
+}
+export {};
+//# sourceMappingURL=sim-cfn-stack-update-plan.d.ts.map

package/dist/service/cloudformation/stack/update/sim-cfn-stack-update-plan.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"sim-cfn-stack-update-plan.d.ts","sourceRoot":"","sources":["../../../../../src/service/cloudformation/stack/update/sim-cfn-stack-update-plan.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,oCAAoC,CAAC;AAGzE,UAAU,+BAA+B;IACvC,QAAQ,CAAC,OAAO,EAAE,WAAW,CAAC,MAAM,EAAE,cAAc,CAAC,CAAC;IACtD,QAAQ,CAAC,OAAO,EAAE,WAAW,CAAC,MAAM,EAAE,cAAc,CAAC,CAAC;CACvD;AAED;;;;;;;;;;;;GAYG;AACH,qBAAa,qBAAqB;IAChC;;;OAGG;IACH,SAAgB,SAAS,EAAE,SAAS,cAAc,EAAE,CAAC;IAErD;;;OAGG;IACH,SAAgB,SAAS,EAAE,SAAS,cAAc,EAAE,CAAC;IAErD,OAAO,CAAC,QAAQ,CAAC,OAAO,CAAsC;IAE9D,YAAY,UAAU,EAAE,+BAA+B,EAwBtD;IAED;;;;;OAKG;IACH,IAAW,gBAAgB,IAAI,OAAO,CAErC;IAED;;;;;;;OAOG;IACH,OAAO,CAAC,SAAS,EAAE,GAAG,CAAC,MAAM,EAAE,cAAc,CAAC,GAAG,IAAI,CAapD;CACF"}

package/dist/service/cloudformation/stack/update/sim-cfn-stack-update-plan.js

@@ -0,0 +1,76 @@
+import { simCfnStackReplacedLogicalIds } from "./sim-cfn-stack-replaced-resources.js";
+/**
+ * What an update has to do to a Stack's Resources, worked out before any of it
+ * happens.
+ *
+ * The plan compares the Resources the Stack has with the ones its new template
+ * describes, and says which to delete, which to create, and what the Stack
+ * holds afterwards. A Resource the template still describes unchanged is left
+ * alone, keeping whatever it holds in simulated AWS.
+ *
+ * It does not delete or create anything, order the work, or decide what counts
+ * as a changed Resource. SimCfnStackUpdater runs the plan, and
+ * simCfnStackReplacedLogicalIds decides what changed.
+ */
+export class SimCfnStackUpdatePlan {
+    /**
+     * The deployed Resources to delete: the ones the new template drops, and the
+     * deployed halves of the ones it replaces.
+     */
+    deletions;
+    /**
+     * The new Resources to create: the ones the new template adds, and the new
+     * halves of the ones it replaces.
+     */
+    creations;
+    updated;
+    constructor(properties) {
+        const { current, updated } = properties;
+        const replaced = simCfnStackReplacedLogicalIds({ current, updated });
+        this.updated = updated;
+        // Both lists are worked out now rather than on demand, because the Stack's
+        // Resource map is the current one and applying the plan changes it.
+        this.deletions = current
+            .values()
+            .filter((resource) => {
+            return (!updated.has(resource.logicalId) || replaced.has(resource.logicalId));
+        })
+            .toArray();
+        this.creations = updated
+            .values()
+            .filter((resource) => {
+            return (!current.has(resource.logicalId) || replaced.has(resource.logicalId));
+        })
+            .toArray();
+    }
+    /**
+     * Whether the update changes any Resource at all.
+     *
+     * A template that only changes something else, such as an Output, still
+     * updates the Stack, so this is not the whole no-op question.
+     */
+    get changesResources() {
+        return this.deletions.length > 0 || this.creations.length > 0;
+    }
+    /**
+     * Move the Stack's Resource map on to the new template.
+     *
+     * The map is changed in place rather than replaced, so anything already
+     * holding the Stack's Resources sees the update. A Resource the template
+     * leaves alone keeps the object it already had, which is what keeps its
+     * simulated AWS Resource and its creation status.
+     */
+    applyTo(resources) {
+        const dropped = resources
+            .keys()
+            .filter((logicalId) => !this.updated.has(logicalId))
+            .toArray();
+        for (const logicalId of dropped) {
+            resources.delete(logicalId);
+        }
+        for (const resource of this.creations) {
+            resources.set(resource.logicalId, resource);
+        }
+    }
+}
+//# sourceMappingURL=sim-cfn-stack-update-plan.js.map