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 Request: fly command for busting credential caches #3896

eedwards-sk opened this issue May 21, 2019 · 0 comments


None yet
2 participants
Copy link

commented May 21, 2019

continuing from #2924

What challenge are you facing?

when credential values are cached (either legitimate values or 'not found' responses, as per #3895), as expected, the new value is not recognized until the cache duration expires

when using a longer cache duration (e.g. 5 minutes or more), this makes it harder to update parameter values during pipeline development or manually performing credential rotations without lowering the cache duration

longer cache durations are useful when running multiple concourse clusters that target e.g. the same AWS SSM api (e.g. developers running local concourse stacks that use the same SSM account will want long cache durations to avoid causing throttling on SSM that could impact production. developers also need to change / update values frequently)

What would make this better?

a fly (api?) command for explicitly busting a credential (parameter) cache

ideally, the specific parameter (for team/pipeline or team) could be targeted, but even coarse grained busting (e.g. for an entire team or team/pipeline) would be useful

Are you interested in implementing this yourself?

No :(

I seek the help of our glorious contributors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.