generated from amazon-archives/__template_Apache-2.0
-
Notifications
You must be signed in to change notification settings - Fork 60
Closed
Labels
Description
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
- Remove cached noticed from
~/.cdk/cache/notices.json. - Run
npx cdk synth --verbose --no-notices- You will see
Notices refreshedin the logs
- You will see
- Run
npx cdk synth --verbose --no-noticesagain- You will see
Reading cached notices from /Users/abcdefg/.cdk/cache/notices.jsonin the logs
- You will see
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
daschaa, lennart-land and xanora