(api-gateway): Ability to set Per-key cache invalidation attributes
- Dominant language
- TypeScript
- Stars
- 12.9k
- Forks
- 4.6k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 83
Description
### Description
It would be great to be able to set Per-key cache invalidation (enabled/disabled) and sub-attributes - Require authorization (true/false) and Handle unauthorized requests (1 from 3 options) globally - per stage and per method in API.
### Use Case
I'm regularly deploying 20+ APIs to 3 stages and have to manually set Per-key cache invalidation behavior manually for each method separately, thats annoying.
### Proposed Solution
Would be great if added these options to interface StageOptions and MethodDeploymentOptions
### Other information
_No response_
### Acknowledge
- [ ] I may be able to implement this feature request
- [ ] This feature might incur a breaking change
Contributor guide
Research direction
Start by locating the StageOptions and MethodDeploymentOptions interfaces and reviewing how API Gateway cache invalidation settings are currently represented. The work is complete when per-key cache invalidation, authorization requirements, and unauthorized-request handling can be configured globally, per stage, and per method.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- api, cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100