Stop Forcing Persistent “Unconfigured Feature Flags” Warnings on New Projects

[ischia-exigenter]

Subject: Stop Forcing Persistent “Unconfigured Feature Flags” Warnings on New Projects

Dear AWS CDK Moderators and Maintainers,

As a developer who relies on the AWS CDK for professional workflows, I am frustrated and disappointed with the persistent “You currently have X unconfigured feature flags that may require attention” warning that now appears on every new project initialized with the official CDK template.

This so-called “helpful” notice is both intrusive and unhelpful. It appears even when a project is freshly bootstrapped with zero customizations, contradicting its own suggestion that configuration is somehow out of date. Worse, all documented suppression techniques (including "notices": false, CLI flags, and context overrides) fail to silence the message—a clear indication that the CDK team is ignoring developer feedback and best practices around user-configurable warnings.

This behavior is:

• Annoying for experienced users who know exactly what they’re doing,
• Deeply confusing for newcomers who think they’ve somehow misconfigured a brand new environment,
• Counterproductive to the “infrastructure as code” philosophy the CDK is supposed to embody.

Ignoring or hiding user-specified configurations and overridable warnings is hostile design, plain and simple. There is no justification for forcing persistent warnings that the user cannot opt out of—particularly in tools intended for automation and repeatable deployment.

The request is simple:
Fix the CDK so that this message either:

• Does NOT appear on brand new projects generated by cdk init with current templates, OR
• Can be completely and reliably suppressed with a documented and honored configuration switch.

I urge you to acknowledge this as a bug—not a feature—and address it as a priority. You are burning good will and undermining developer trust. Please listen to your community and do better.

Sincerely,
A frustrated AWS CDK user