cdk-preflight 0.0.53__py3-none-any.whl

cdk_preflight/__init__.py

@@ -0,0 +1,363 @@
+r'''
+<p align="center">
+  <img src="https://raw.githubusercontent.com/badmintoncryer/cdk-preflight/main/assets/logo.png" alt="cdk-preflight" width="104" height="104">
+</p><h1 align="center">cdk-preflight</h1><p align="center">
+  <strong>Catch deploy-time CloudFormation failures at <code>cdk synth</code> time.</strong>
+</p><p align="center">
+  <a href="https://github.com/badmintoncryer/cdk-preflight/actions/workflows/monthly-verify.yml"><img src="https://github.com/badmintoncryer/cdk-preflight/actions/workflows/monthly-verify.yml/badge.svg" alt="monthly real-deploy verification"></a>
+  <a href="https://www.npmjs.com/package/cdk-preflight"><img src="https://img.shields.io/npm/v/cdk-preflight.svg" alt="npm version"></a>
+  <a href="https://www.npmjs.com/package/cdk-preflight"><img src="https://img.shields.io/npm/dt/cdk-preflight.svg" alt="npm total downloads"></a>
+</p>
+
+Some CloudFormation constraints are not expressed in resource provider schemas — they live only in documentation, in service API validation, or across multiple properties. Templates that violate them pass `cdk synth`, pass CloudFormation pre-deployment validation, and then fail minutes into a deployment, burning a rollback cycle.
+
+cdk-preflight is a curated [Rego rule pack](docs/rules.md) for exactly those constraints, evaluated with the CloudFormation validation engine that ships inside `aws-cdk-lib` (>= 2.267.0). By default a violation **fails `cdk synth`** — a template that is known to fail at deploy time never leaves your machine.
+
+The pack aims at **every deploy-time failure that no existing CDK mechanism already catches** — nothing narrower. Every bundled rule is backed by a `fail`/`pass` template pair, and the failure has been reproduced against real AWS (or is explicitly marked `doc-only`). Rules that the built-in validation engine already covers are deliberately **not** duplicated — a test suite enforces this.
+
+> **Requires `aws-cdk-lib` >= 2.267.0** (released 2026-08-27) — the first release that bundles
+> the CloudFormation validation engine. On older versions the rules cannot run at all.
+
+## Quick start
+
+```bash
+npm i -D cdk-preflight
+npx cdkpf init   # inserts Preflight.apply(app) into your CDK app
+                         # (`npx cdkpf init` is the same command, shorter)
+```
+
+or add one line yourself:
+
+```python
+import { Preflight } from 'cdk-preflight';
+
+const app = new App();
+Preflight.apply(app);
+```
+
+On violation, `cdk synth` fails with one error per finding, including the construct trace:
+
+```text
+ERROR idle_timeout.timeout_seconds is 5000 but must be between 1 and 4000 seconds (cdk-preflight)
+   MyStack/Alb/Resource (Alb16C2F182) aws-cdk-lib.aws_elasticloadbalancingv2.CfnLoadBalancer
+
+Synthesis finished with errors
+```
+
+## Observe-only mode
+
+To roll the rules out gradually, start with `enforce: false`: findings then surface as synth **warnings** through the CDK built-in validator, with construct traces and per-finding acknowledgement:
+
+```python
+Preflight.apply(app, { enforce: false });
+```
+
+```text
+WARNING idle_timeout.timeout_seconds is 5000 but must be between 1 and 4000 seconds (CloudFormation Validate)
+   MyStack/Alb (Alb) aws-cdk-lib.aws_elasticloadbalancingv2.CfnLoadBalancer
+   Acknowledge with 'CloudFormation-Validate::pf-elbv2-lb-idle-timeout-range'
+```
+
+> **Known limitation with stages.** The AWS CDK CLI drops validation findings for stacks nested in a `Stage`
+> before printing them, so in observe-only mode those findings appear **only** in `cdk.out/validation-report.json`
+> and never on the console. Enforce mode is not affected: cdk-preflight reports such findings itself and fails
+> synthesis. This is a CLI-side bug (present since aws-cdk 2.1128.1), not a rule evaluation problem.
+
+| Option | Default | Effect |
+|---|---|---|
+| `enforce` | `true` | Violations of bundled rules fail synthesis; set to `false` to only warn |
+| `strict` | `false` | With `enforce`: also fail on error-class findings (`ERROR`/`FATAL`, e.g. `F3034`) of the built-in validation engine itself, which the CDK currently downgrades to warnings |
+| `exclude` | `[]` | Rule ids to disable |
+| `includeUpstreamPending` | `true` | Include rules already proposed to the upstream engine but not yet merged |
+
+To opt out of a single rule, pass its id in `exclude`. In observe-only mode, individual findings can also be suppressed with the CDK acknowledge mechanism shown in the warning text.
+
+## Bundled rules
+
+See [docs/rules.md](docs/rules.md) for the generated rule table. Highlights:
+
+* **ELBv2**: `idle_timeout` / `deregistration_delay` / `slow_start` attribute ranges (stringly-typed Key/Value attributes are invisible to schema validation)
+* **IAM**: managed (6,144 chars) and inline (role/group/user) policy document size limits
+* **CloudFront**: `MinTTL <= DefaultTTL <= MaxTTL` ordering, ACM certificates must live in `us-east-1`
+* **Step Functions**: `Next`/`Default`/`Choices` must reference defined states (a dangling `StartAt` is already caught by the engine's built-in `E3601`)
+* **EC2**: security group TCP/UDP port ranges and `FromPort <= ToPort`
+
+## For AI agents
+
+To add cdk-preflight to a CDK app:
+
+1. `npm i -D cdk-preflight`
+2. `npx cdk-preflight init` — or the shorter alias `npx cdkpf init` (finds the entry point via `cdk.json` and inserts `Preflight.apply(app)`; use `--dry-run` to preview)
+3. Run `cdk synth`. Violations fail the synth with a validation report; each finding carries a rule id, the actual value, and a suggested fix
+4. To fix a finding, prefer correcting the resource. To opt out instead: `exclude: ['<rule-id>']` disables one rule, `enforce: false` switches to warn-only reporting
+
+The machine-readable findings are written to `cdk.out/validation-report.json` when synthesizing with `-c @aws-cdk/core:validationReportJson=true`.
+
+### Report missed deploy errors
+
+cdk-preflight only knows the failure modes it has benched. When a deploy fails on a constraint the pack should have caught, that report is how new rules get added — but at that moment cdk-preflight is out of the loop (it passed the synth), so the instruction has to already sit in your agent's context. Paste this into your repository's `AGENTS.md` (or `CLAUDE.md`):
+
+```markdown
+## cdk-preflight: report missed deploy errors
+
+If `cdk deploy` fails even though `cdk synth` (with cdk-preflight enabled) passed,
+and the failure is a service-side validation rejection — CREATE_FAILED/UPDATE_FAILED
+with a 400-class message such as "Invalid request provided: ..." — cdk-preflight is
+missing a rule. Report it:
+
+1. Qualify first. NOT reportable: AccessDenied / permissions, service quotas,
+   throttling, name conflicts with existing resources, stabilization timeouts.
+2. Redact account-specific data (account IDs -> 123456789012, real ARNs/domains
+   -> placeholders).
+3. Search existing issues: https://github.com/badmintoncryer/cdk-preflight/issues
+4. With your user's approval, open a "Missed deploy error" issue with the verbatim
+   error message, the resource type, a minimal template snippet, and your
+   aws-cdk-lib / cdk-preflight versions.
+```
+
+## Scope and rule lifecycle
+
+A constraint belongs in the pack when violating it makes a real deployment fail *and* no layer that sees the same synthesized template already blocks it. There is no further "is this worth a rule" question — if the gap is real, it gets a rule.
+
+CDK L2 construct validation is deliberately **not** one of those layers. `CfnXxx` usage, escape hatches, `addPropertyOverride`, `cloudformation-include` and migrated templates all bypass L2, so an L2 guard covering the same mistake neither disqualifies a rule nor retires one.
+
+That makes growth the normal state, and it has a consequence worth knowing before you upgrade: **new rules land in minor releases, so a minor upgrade can newly fail a `cdk synth` that passed yesterday.** That is intended, not a regression. If you need a frozen rule set, pin the version; to drop a single rule, `exclude: ['<rule-id>']`; to see everything without failing the build, `enforce: false`.
+
+Rules move the other way too. Once the validation engine bundled in `aws-cdk-lib` (or CloudFormation's own pre-deploy validation) starts blocking a constraint, the rule is deleted rather than kept as a duplicate — staying on an older `aws-cdk-lib` and an older cdk-preflight keeps the old behavior.
+
+## How it works
+
+`Preflight.apply()` evaluates the rules with the [cloudformation-validate](https://github.com/aws-cloudformation/cloudformation-validate) Rust/WASM engine that ships inside `aws-cdk-lib` — no extra binaries, no network access at synth time. In the default enforce mode the engine is invoked through a dedicated CDK validation plugin so that violations fail synthesis; with `enforce: false` the rules are instead injected into the CDK built-in `CloudFormationValidatePlugin` and reported as warnings.
+
+Constraints that *can* be expressed in schemas or generic engine rules also make good upstream PRs to that engine, but nothing here waits on one — the upstream release cycle is deliberately slower than this pack's. Each rule's `meta.yaml` tracks its upstream status so that retirement stays bookkeeping.
+
+## Requirements
+
+* `aws-cdk-lib` >= 2.267.0, released 2026-08-27 (the first release that bundles the built-in CloudFormation validator). This is a recent release — an existing CDK app may need an upgrade before cdk-preflight can run.
+
+## Contributing
+
+Rule authoring, the verification gates (including real-deploy reproduction), and the test layout are documented in [AGENTS.md](AGENTS.md) — written for AI coding agents and humans alike.
+
+## License
+
+Apache-2.0
+'''
+from __future__ import annotations
+
+from pkgutil import extend_path
+__path__ = extend_path(__path__, __name__)
+
+import abc
+import builtins
+import datetime
+import enum
+import typing
+
+import jsii
+import publication
+import typing_extensions
+
+from jsii._type_checking import cached_type_hints, check_type
+
+
+from ._jsii import *
+
+class _LazyImport:
+    def __init__(self, module_name: str) -> None:
+        self._module_name = module_name
+        self._module: typing.Any = None
+    def __getattr__(self, name: str) -> typing.Any:
+        if self._module is None:
+            import importlib
+            self._module = importlib.import_module(self._module_name)
+        return getattr(self._module, name)
+
+if typing.TYPE_CHECKING:
+
+    import constructs as _constructs_77d1e7e8
+else:
+
+    _constructs_77d1e7e8 = _LazyImport("constructs")
+
+
+class Preflight(metaclass=jsii.JSIIMeta, jsii_type="cdk-preflight.Preflight"):
+    '''cdk-preflight: catch deploy-time CloudFormation failures at synth time.
+
+    Injects a curated Rego rule pack (constraints that resource provider schemas
+    do not express: doc-only value limits, cross-property and cross-resource
+    rules) into the AWS CDK built-in CloudFormation validator.
+
+    Example::
+
+        declare const app: App;
+        Preflight.apply(app);
+    '''
+
+    @jsii.member(jsii_name="apply")
+    @builtins.classmethod
+    def apply(
+        cls,
+        scope: "_constructs_77d1e7e8.IConstruct",
+        *,
+        enforce: typing.Optional[builtins.bool] = None,
+        exclude: typing.Optional[typing.Sequence[builtins.str]] = None,
+        include_upstream_pending: typing.Optional[builtins.bool] = None,
+        strict: typing.Optional[builtins.bool] = None,
+    ) -> None:
+        '''Register the cdk-preflight rules on an App or Stage.
+
+        :param scope: -
+        :param enforce: Fail synthesis when a bundled rule is violated. In the default (enforce) mode, cdk-preflight evaluates its rules with its own validation plugin and a violation makes ``cdk synth`` fail — the whole point of preflight checks is that a template known to fail at deploy time never leaves your machine. Set ``enforce: false`` to observe first: findings are then reported through the CDK built-in CloudFormation validator and surface as synth warnings with construct traces, which can be muted per finding via ``Acknowledge with 'CloudFormation-Validate::<rule-id>'``. Default: true
+        :param exclude: Rule ids to disable (see ``Preflight.ruleIds()`` or docs/rules.md). Default: - all bundled rules are enabled
+        :param include_upstream_pending: Include rules that are marked ``pending-engine`` (candidates that have been proposed to the upstream cloudformation-validate engine but are not merged yet). Disable this if you run a newer engine that already covers them. Default: true
+        :param strict: In enforce mode, additionally fail synthesis on error-class findings (severity ERROR/FATAL) of the built-in validation engine itself, e.g. schema violations like ``F3034``. This is the workaround for the CDK behavior where all built-in findings are downgraded to warnings. Only effective in enforce mode (the default). Default: false
+        '''
+        if __debug__:
+            type_hints = cached_type_hints(_typecheckingstub__5b535ea6056dfabd62239bba1185a75fb43155b62d18b3cbb69ca8a01b7edfa8)
+            check_type(argname="argument scope", value=scope, expected_type=type_hints["scope"])
+        options = PreflightOptions(
+            enforce=enforce,
+            exclude=exclude,
+            include_upstream_pending=include_upstream_pending,
+            strict=strict,
+        )
+
+        return typing.cast(None, jsii.sinvoke(cls, "apply", [scope, options]))
+
+    @jsii.member(jsii_name="ruleIds")
+    @builtins.classmethod
+    def rule_ids(cls) -> typing.List[builtins.str]:
+        '''The ids of all bundled rules.'''
+        return typing.cast(typing.List[builtins.str], jsii.sinvoke(cls, "ruleIds", []))
+
+
+@jsii.data_type(
+    jsii_type="cdk-preflight.PreflightOptions",
+    jsii_struct_bases=[],
+    name_mapping={
+        "enforce": "enforce",
+        "exclude": "exclude",
+        "include_upstream_pending": "includeUpstreamPending",
+        "strict": "strict",
+    },
+)
+class PreflightOptions:
+    def __init__(
+        self,
+        *,
+        enforce: typing.Optional[builtins.bool] = None,
+        exclude: typing.Optional[typing.Sequence[builtins.str]] = None,
+        include_upstream_pending: typing.Optional[builtins.bool] = None,
+        strict: typing.Optional[builtins.bool] = None,
+    ) -> None:
+        '''Options for {@link Preflight.apply}.
+
+        :param enforce: Fail synthesis when a bundled rule is violated. In the default (enforce) mode, cdk-preflight evaluates its rules with its own validation plugin and a violation makes ``cdk synth`` fail — the whole point of preflight checks is that a template known to fail at deploy time never leaves your machine. Set ``enforce: false`` to observe first: findings are then reported through the CDK built-in CloudFormation validator and surface as synth warnings with construct traces, which can be muted per finding via ``Acknowledge with 'CloudFormation-Validate::<rule-id>'``. Default: true
+        :param exclude: Rule ids to disable (see ``Preflight.ruleIds()`` or docs/rules.md). Default: - all bundled rules are enabled
+        :param include_upstream_pending: Include rules that are marked ``pending-engine`` (candidates that have been proposed to the upstream cloudformation-validate engine but are not merged yet). Disable this if you run a newer engine that already covers them. Default: true
+        :param strict: In enforce mode, additionally fail synthesis on error-class findings (severity ERROR/FATAL) of the built-in validation engine itself, e.g. schema violations like ``F3034``. This is the workaround for the CDK behavior where all built-in findings are downgraded to warnings. Only effective in enforce mode (the default). Default: false
+        '''
+        if __debug__:
+            type_hints = cached_type_hints(_typecheckingstub__12ab0dc6052d00feef3e218547f7a8add8c0a9bd629d0362a30a71aa52b7cab1)
+            check_type(argname="argument enforce", value=enforce, expected_type=type_hints["enforce"])
+            check_type(argname="argument exclude", value=exclude, expected_type=type_hints["exclude"])
+            check_type(argname="argument include_upstream_pending", value=include_upstream_pending, expected_type=type_hints["include_upstream_pending"])
+            check_type(argname="argument strict", value=strict, expected_type=type_hints["strict"])
+        self._values: typing.Dict[builtins.str, typing.Any] = {}
+        if enforce is not None:
+            self._values["enforce"] = enforce
+        if exclude is not None:
+            self._values["exclude"] = exclude
+        if include_upstream_pending is not None:
+            self._values["include_upstream_pending"] = include_upstream_pending
+        if strict is not None:
+            self._values["strict"] = strict
+
+    @builtins.property
+    def enforce(self) -> typing.Optional[builtins.bool]:
+        '''Fail synthesis when a bundled rule is violated.
+
+        In the default (enforce) mode, cdk-preflight evaluates its rules with its
+        own validation plugin and a violation makes ``cdk synth`` fail — the whole
+        point of preflight checks is that a template known to fail at deploy time
+        never leaves your machine. Set ``enforce: false`` to observe first: findings
+        are then reported through the CDK built-in CloudFormation validator and
+        surface as synth warnings with construct traces, which can be muted per
+        finding via ``Acknowledge with 'CloudFormation-Validate::<rule-id>'``.
+
+        :default: true
+        '''
+        result = self._values.get("enforce")
+        return typing.cast(typing.Optional[builtins.bool], result)
+
+    @builtins.property
+    def exclude(self) -> typing.Optional[typing.List[builtins.str]]:
+        '''Rule ids to disable (see ``Preflight.ruleIds()`` or docs/rules.md).
+
+        :default: - all bundled rules are enabled
+        '''
+        result = self._values.get("exclude")
+        return typing.cast(typing.Optional[typing.List[builtins.str]], result)
+
+    @builtins.property
+    def include_upstream_pending(self) -> typing.Optional[builtins.bool]:
+        '''Include rules that are marked ``pending-engine`` (candidates that have been proposed to the upstream cloudformation-validate engine but are not merged yet).
+
+        Disable this if you run a newer engine that already covers them.
+
+        :default: true
+        '''
+        result = self._values.get("include_upstream_pending")
+        return typing.cast(typing.Optional[builtins.bool], result)
+
+    @builtins.property
+    def strict(self) -> typing.Optional[builtins.bool]:
+        '''In enforce mode, additionally fail synthesis on error-class findings (severity ERROR/FATAL) of the built-in validation engine itself, e.g. schema violations like ``F3034``. This is the workaround for the CDK behavior where all built-in findings are downgraded to warnings.
+
+        Only effective in enforce mode (the default).
+
+        :default: false
+        '''
+        result = self._values.get("strict")
+        return typing.cast(typing.Optional[builtins.bool], result)
+
+    def __eq__(self, rhs: typing.Any) -> builtins.bool:
+        return isinstance(rhs, self.__class__) and rhs._values == self._values
+
+    def __ne__(self, rhs: typing.Any) -> builtins.bool:
+        return not (rhs == self)
+
+    def __repr__(self) -> str:
+        return "PreflightOptions(%s)" % ", ".join(
+            k + "=" + repr(v) for k, v in self._values.items()
+        )
+
+
+__all__ = [
+    "Preflight",
+    "PreflightOptions",
+]
+
+publication.publish()
+
+def _typecheckingstub__5b535ea6056dfabd62239bba1185a75fb43155b62d18b3cbb69ca8a01b7edfa8(
+    scope: _constructs_77d1e7e8.IConstruct,
+    *,
+    enforce: typing.Optional[builtins.bool] = None,
+    exclude: typing.Optional[typing.Sequence[builtins.str]] = None,
+    include_upstream_pending: typing.Optional[builtins.bool] = None,
+    strict: typing.Optional[builtins.bool] = None,
+) -> None:
+    """Type checking stubs"""
+    pass
+
+def _typecheckingstub__12ab0dc6052d00feef3e218547f7a8add8c0a9bd629d0362a30a71aa52b7cab1(
+    *,
+    enforce: typing.Optional[builtins.bool] = None,
+    exclude: typing.Optional[typing.Sequence[builtins.str]] = None,
+    include_upstream_pending: typing.Optional[builtins.bool] = None,
+    strict: typing.Optional[builtins.bool] = None,
+) -> None:
+    """Type checking stubs"""
+    pass

cdk_preflight/_jsii/__init__.py

@@ -0,0 +1,28 @@
+from pkgutil import extend_path
+__path__ = extend_path(__path__, __name__)
+
+import abc
+import builtins
+import datetime
+import enum
+import typing
+
+import jsii
+import publication
+import typing_extensions
+
+from jsii._type_checking import cached_type_hints, check_type
+
+
+import aws_cdk._jsii
+import constructs._jsii
+
+__jsii_assembly__ = jsii.JSIIAssembly.load(
+    "cdk-preflight", "0.0.53", __name__[0:-6], "cdk-preflight@0.0.53.jsii.tgz"
+)
+
+__all__ = [
+    "__jsii_assembly__",
+]
+
+publication.publish()

cdk_preflight/py.typed

@@ -0,0 +1 @@
+

cdk_preflight-0.0.53.data/scripts/cdk-preflight

@@ -0,0 +1,17 @@
+#!python
+
+import jsii
+import sys
+import os
+
+if "JSII_RUNTIME_PACKAGE_CACHE" not in os.environ:
+    os.environ["JSII_RUNTIME_PACKAGE_CACHE"] = "disabled"
+
+__jsii_assembly__ = jsii.JSIIAssembly.load(
+    "cdk-preflight", "0.0.53", "cdk_preflight", "cdk-preflight@0.0.53.jsii.tgz"
+)
+
+exit_code = __jsii_assembly__.invokeBinScript(
+    "cdk-preflight", "cdk-preflight", sys.argv[1:]
+)
+exit(exit_code)

cdk_preflight-0.0.53.data/scripts/cdkpf

@@ -0,0 +1,15 @@
+#!python
+
+import jsii
+import sys
+import os
+
+if "JSII_RUNTIME_PACKAGE_CACHE" not in os.environ:
+    os.environ["JSII_RUNTIME_PACKAGE_CACHE"] = "disabled"
+
+__jsii_assembly__ = jsii.JSIIAssembly.load(
+    "cdk-preflight", "0.0.53", "cdk_preflight", "cdk-preflight@0.0.53.jsii.tgz"
+)
+
+exit_code = __jsii_assembly__.invokeBinScript("cdk-preflight", "cdkpf", sys.argv[1:])
+exit(exit_code)

cdk_preflight-0.0.53.dist-info/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

cdk_preflight-0.0.53.dist-info/METADATA

@@ -0,0 +1,171 @@
+Metadata-Version: 2.1
+Name: cdk-preflight
+Version: 0.0.53
+Summary: Catch deploy-time CloudFormation failures at synth time: a Rego rule pack for constraints that resource schemas miss, injected into the AWS CDK built-in validator
+Home-page: https://github.com/badmintoncryer/cdk-preflight.git
+Author: Kazuho CryerShinozuka<malaysia.cryer@gmail.com>
+License: Apache-2.0
+Project-URL: Source, https://github.com/badmintoncryer/cdk-preflight.git
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: JavaScript
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Typing :: Typed
+Classifier: Development Status :: 5 - Production/Stable
+Classifier: License :: OSI Approved
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: aws-cdk-lib <3.0.0,>=2.267.0
+Requires-Dist: constructs <11.0.0,>=10.5.1
+Requires-Dist: jsii <2.0.0,>=1.140.0
+Requires-Dist: publication >=0.0.3
+
+<p align="center">
+  <img src="https://raw.githubusercontent.com/badmintoncryer/cdk-preflight/main/assets/logo.png" alt="cdk-preflight" width="104" height="104">
+</p><h1 align="center">cdk-preflight</h1><p align="center">
+  <strong>Catch deploy-time CloudFormation failures at <code>cdk synth</code> time.</strong>
+</p><p align="center">
+  <a href="https://github.com/badmintoncryer/cdk-preflight/actions/workflows/monthly-verify.yml"><img src="https://github.com/badmintoncryer/cdk-preflight/actions/workflows/monthly-verify.yml/badge.svg" alt="monthly real-deploy verification"></a>
+  <a href="https://www.npmjs.com/package/cdk-preflight"><img src="https://img.shields.io/npm/v/cdk-preflight.svg" alt="npm version"></a>
+  <a href="https://www.npmjs.com/package/cdk-preflight"><img src="https://img.shields.io/npm/dt/cdk-preflight.svg" alt="npm total downloads"></a>
+</p>
+
+Some CloudFormation constraints are not expressed in resource provider schemas — they live only in documentation, in service API validation, or across multiple properties. Templates that violate them pass `cdk synth`, pass CloudFormation pre-deployment validation, and then fail minutes into a deployment, burning a rollback cycle.
+
+cdk-preflight is a curated [Rego rule pack](docs/rules.md) for exactly those constraints, evaluated with the CloudFormation validation engine that ships inside `aws-cdk-lib` (>= 2.267.0). By default a violation **fails `cdk synth`** — a template that is known to fail at deploy time never leaves your machine.
+
+The pack aims at **every deploy-time failure that no existing CDK mechanism already catches** — nothing narrower. Every bundled rule is backed by a `fail`/`pass` template pair, and the failure has been reproduced against real AWS (or is explicitly marked `doc-only`). Rules that the built-in validation engine already covers are deliberately **not** duplicated — a test suite enforces this.
+
+> **Requires `aws-cdk-lib` >= 2.267.0** (released 2026-08-27) — the first release that bundles
+> the CloudFormation validation engine. On older versions the rules cannot run at all.
+
+## Quick start
+
+```bash
+npm i -D cdk-preflight
+npx cdkpf init   # inserts Preflight.apply(app) into your CDK app
+                         # (`npx cdkpf init` is the same command, shorter)
+```
+
+or add one line yourself:
+
+```python
+import { Preflight } from 'cdk-preflight';
+
+const app = new App();
+Preflight.apply(app);
+```
+
+On violation, `cdk synth` fails with one error per finding, including the construct trace:
+
+```text
+ERROR idle_timeout.timeout_seconds is 5000 but must be between 1 and 4000 seconds (cdk-preflight)
+   MyStack/Alb/Resource (Alb16C2F182) aws-cdk-lib.aws_elasticloadbalancingv2.CfnLoadBalancer
+
+Synthesis finished with errors
+```
+
+## Observe-only mode
+
+To roll the rules out gradually, start with `enforce: false`: findings then surface as synth **warnings** through the CDK built-in validator, with construct traces and per-finding acknowledgement:
+
+```python
+Preflight.apply(app, { enforce: false });
+```
+
+```text
+WARNING idle_timeout.timeout_seconds is 5000 but must be between 1 and 4000 seconds (CloudFormation Validate)
+   MyStack/Alb (Alb) aws-cdk-lib.aws_elasticloadbalancingv2.CfnLoadBalancer
+   Acknowledge with 'CloudFormation-Validate::pf-elbv2-lb-idle-timeout-range'
+```
+
+> **Known limitation with stages.** The AWS CDK CLI drops validation findings for stacks nested in a `Stage`
+> before printing them, so in observe-only mode those findings appear **only** in `cdk.out/validation-report.json`
+> and never on the console. Enforce mode is not affected: cdk-preflight reports such findings itself and fails
+> synthesis. This is a CLI-side bug (present since aws-cdk 2.1128.1), not a rule evaluation problem.
+
+| Option | Default | Effect |
+|---|---|---|
+| `enforce` | `true` | Violations of bundled rules fail synthesis; set to `false` to only warn |
+| `strict` | `false` | With `enforce`: also fail on error-class findings (`ERROR`/`FATAL`, e.g. `F3034`) of the built-in validation engine itself, which the CDK currently downgrades to warnings |
+| `exclude` | `[]` | Rule ids to disable |
+| `includeUpstreamPending` | `true` | Include rules already proposed to the upstream engine but not yet merged |
+
+To opt out of a single rule, pass its id in `exclude`. In observe-only mode, individual findings can also be suppressed with the CDK acknowledge mechanism shown in the warning text.
+
+## Bundled rules
+
+See [docs/rules.md](docs/rules.md) for the generated rule table. Highlights:
+
+* **ELBv2**: `idle_timeout` / `deregistration_delay` / `slow_start` attribute ranges (stringly-typed Key/Value attributes are invisible to schema validation)
+* **IAM**: managed (6,144 chars) and inline (role/group/user) policy document size limits
+* **CloudFront**: `MinTTL <= DefaultTTL <= MaxTTL` ordering, ACM certificates must live in `us-east-1`
+* **Step Functions**: `Next`/`Default`/`Choices` must reference defined states (a dangling `StartAt` is already caught by the engine's built-in `E3601`)
+* **EC2**: security group TCP/UDP port ranges and `FromPort <= ToPort`
+
+## For AI agents
+
+To add cdk-preflight to a CDK app:
+
+1. `npm i -D cdk-preflight`
+2. `npx cdk-preflight init` — or the shorter alias `npx cdkpf init` (finds the entry point via `cdk.json` and inserts `Preflight.apply(app)`; use `--dry-run` to preview)
+3. Run `cdk synth`. Violations fail the synth with a validation report; each finding carries a rule id, the actual value, and a suggested fix
+4. To fix a finding, prefer correcting the resource. To opt out instead: `exclude: ['<rule-id>']` disables one rule, `enforce: false` switches to warn-only reporting
+
+The machine-readable findings are written to `cdk.out/validation-report.json` when synthesizing with `-c @aws-cdk/core:validationReportJson=true`.
+
+### Report missed deploy errors
+
+cdk-preflight only knows the failure modes it has benched. When a deploy fails on a constraint the pack should have caught, that report is how new rules get added — but at that moment cdk-preflight is out of the loop (it passed the synth), so the instruction has to already sit in your agent's context. Paste this into your repository's `AGENTS.md` (or `CLAUDE.md`):
+
+```markdown
+## cdk-preflight: report missed deploy errors
+
+If `cdk deploy` fails even though `cdk synth` (with cdk-preflight enabled) passed,
+and the failure is a service-side validation rejection — CREATE_FAILED/UPDATE_FAILED
+with a 400-class message such as "Invalid request provided: ..." — cdk-preflight is
+missing a rule. Report it:
+
+1. Qualify first. NOT reportable: AccessDenied / permissions, service quotas,
+   throttling, name conflicts with existing resources, stabilization timeouts.
+2. Redact account-specific data (account IDs -> 123456789012, real ARNs/domains
+   -> placeholders).
+3. Search existing issues: https://github.com/badmintoncryer/cdk-preflight/issues
+4. With your user's approval, open a "Missed deploy error" issue with the verbatim
+   error message, the resource type, a minimal template snippet, and your
+   aws-cdk-lib / cdk-preflight versions.
+```
+
+## Scope and rule lifecycle
+
+A constraint belongs in the pack when violating it makes a real deployment fail *and* no layer that sees the same synthesized template already blocks it. There is no further "is this worth a rule" question — if the gap is real, it gets a rule.
+
+CDK L2 construct validation is deliberately **not** one of those layers. `CfnXxx` usage, escape hatches, `addPropertyOverride`, `cloudformation-include` and migrated templates all bypass L2, so an L2 guard covering the same mistake neither disqualifies a rule nor retires one.
+
+That makes growth the normal state, and it has a consequence worth knowing before you upgrade: **new rules land in minor releases, so a minor upgrade can newly fail a `cdk synth` that passed yesterday.** That is intended, not a regression. If you need a frozen rule set, pin the version; to drop a single rule, `exclude: ['<rule-id>']`; to see everything without failing the build, `enforce: false`.
+
+Rules move the other way too. Once the validation engine bundled in `aws-cdk-lib` (or CloudFormation's own pre-deploy validation) starts blocking a constraint, the rule is deleted rather than kept as a duplicate — staying on an older `aws-cdk-lib` and an older cdk-preflight keeps the old behavior.
+
+## How it works
+
+`Preflight.apply()` evaluates the rules with the [cloudformation-validate](https://github.com/aws-cloudformation/cloudformation-validate) Rust/WASM engine that ships inside `aws-cdk-lib` — no extra binaries, no network access at synth time. In the default enforce mode the engine is invoked through a dedicated CDK validation plugin so that violations fail synthesis; with `enforce: false` the rules are instead injected into the CDK built-in `CloudFormationValidatePlugin` and reported as warnings.
+
+Constraints that *can* be expressed in schemas or generic engine rules also make good upstream PRs to that engine, but nothing here waits on one — the upstream release cycle is deliberately slower than this pack's. Each rule's `meta.yaml` tracks its upstream status so that retirement stays bookkeeping.
+
+## Requirements
+
+* `aws-cdk-lib` >= 2.267.0, released 2026-08-27 (the first release that bundles the built-in CloudFormation validator). This is a recent release — an existing CDK app may need an upgrade before cdk-preflight can run.
+
+## Contributing
+
+Rule authoring, the verification gates (including real-deploy reproduction), and the test layout are documented in [AGENTS.md](AGENTS.md) — written for AI coding agents and humans alike.
+
+## License
+
+Apache-2.0

cdk_preflight-0.0.53.dist-info/RECORD

@@ -0,0 +1,11 @@
+cdk_preflight/__init__.py,sha256=A1HOln9rJVC3MWQ4Aa64sAtPduMs22Ut_4sckdGGgT0,20269
+cdk_preflight/py.typed,sha256=AbpHGcgLb-kRsJGnwFEktk7uzpZOCcBY74-YBdrKVGs,1
+cdk_preflight/_jsii/__init__.py,sha256=fG64si-btQvcdVPsMndINI5eEl70kJW2MtMFvdh93G8,501
+cdk_preflight/_jsii/cdk-preflight@0.0.53.jsii.tgz,sha256=iFE0Y5syDS5BVE6PKotOy1ntq1nCEAoVLMJSr-i9Jhw,779957
+cdk_preflight-0.0.53.data/scripts/cdk-preflight,sha256=8dAw8dA39nfm2UO5shQqOyRrxirTlUbYSGPCFgySZN4,397
+cdk_preflight-0.0.53.data/scripts/cdkpf,sha256=8-bx69OKAVRKQtDHwOlCnDSqdoLnwgxYfhGokzuYiRQ,383
+cdk_preflight-0.0.53.dist-info/LICENSE,sha256=z8d0m5b2O9McPEK1xHG_dWgUBT6EfBDz6wA0F7xSPTA,11358
+cdk_preflight-0.0.53.dist-info/METADATA,sha256=9QFTYH2r__v0Z6uFRP_5CG83N2b5GCSm4XHYo-npx9M,10903
+cdk_preflight-0.0.53.dist-info/WHEEL,sha256=BNRMDyzLkkcmlv0J8ppDQkk2VED33SesJDynr9ED1gc,91
+cdk_preflight-0.0.53.dist-info/top_level.txt,sha256=hUIh41e1ILkhjLPiFKniCK0AiWdNju6JIRE-5PzSpEo,14
+cdk_preflight-0.0.53.dist-info/RECORD,,

cdk_preflight-0.0.53.dist-info/WHEEL

@@ -0,0 +1,5 @@
+Wheel-Version: 1.0
+Generator: setuptools (75.3.4)
+Root-Is-Purelib: true
+Tag: py3-none-any
+

cdk_preflight-0.0.53.dist-info/top_level.txt

@@ -0,0 +1 @@
+cdk_preflight