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

feature: Response caching #328

Open
niallthomson opened this issue Feb 4, 2025 · 0 comments
Open

feature: Response caching #328

niallthomson opened this issue Feb 4, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@niallthomson
Copy link
Contributor

🔖 Feature description

For many plugins it would be good to have some sort of response caching to enable faster response times and less calls to the AWS APIs. This should be implemented consistently across plugins, providing an opportunity to enable/disable and specific a TTL for each plugin.

aws:
  ecs:
    caching:
      enable: true
      ttl: 360
  codepipeline:
    caching:
      enable: true
      ttl: 60

Caching should always be disabled by default to avoid confusion.

This caching will have to take in to account RBAC considerations, for example if a user tries to access information related to a catalog entry that they do not have permissions to view.

🎤 Context

N/A

✌️ Possible Implementation

No response

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

No branches or pull requests

1 participant