Skip to content

(cli): --no-notices flag still gets notices when no cached version present #473

@tenjaa

Description

@tenjaa

Describe the bug

It seems that when no cached notices are available, the cli tries to update the notices even though --no-notices is set.

Regression Issue

  • Select this option if this issue appears to be a regression.

Last Known Working CDK Version

No response

Expected Behavior

When --no-notices is set, the cdk does not try to connect to cli.cdk.dev-tools.aws.dev

Current Behavior

When --no-notices is set, the cdk does try to connect to cli.cdk.dev-tools.aws.dev

Reproduction Steps

  1. Remove cached noticed from ~/.cdk/cache/notices.json.
  2. Run npx cdk synth --verbose --no-notices
    • You will see Notices refreshed in the logs
  3. Run npx cdk synth --verbose --no-notices again
    • You will see Reading cached notices from /Users/abcdefg/.cdk/cache/notices.json in the logs

Possible Solution

No response

Additional Information/Context

No response

CDK CLI Version

2.1012.0 (build e4c1f15)

Framework Version

No response

Node.js Version

22

OS

osx

Language

TypeScript

Language Version

No response

Other information

No response

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions