Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[AWS::ApiGateway::Stage] - [BUG] - caching remains enabled after removal, potentially returning wrong data #2231

Open
apparentorder opened this issue Jan 11, 2025 · 0 comments
Labels

Comments

@apparentorder
Copy link

Name of the resource

AWS::ApiGateway::Stage

Resource Name

No response

Issue Description

Removing the cache_enabled and cache_cluster_enabled settings from stage deployment options does not disable caching, as is the default behavior, despite cdk diff output suggesting it would be removed.

Side note: When trying to disabe caching entirely, the caching keys configuration might be removed at the same time. In this case, due to this bug, caching remains enabled but the caching keys are not respected anymore, which leads to caching/delivery of randomly wrong data to clients, causing havoc and mayhem.

Expected Behavior

The resource is configured just like it would be when it is initially created with the given template. (caching is disabled)

Observed Behavior

The resource is configured differently from how it would be initially created with the given template. (caching is enabled)

Test Cases

For complete details and test case, please refer to aws/aws-cdk#32342. Your colleagues asked me to create this issue here, as they suggest the root problem is with CFn, so I'm just relaying their message.

Other Details

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant