Add invalidate cache endpoint #178
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Is this ready to merge/review? |
|
Now |
jakubno
commented
Sep 18, 2024
| @@ -192,7 +192,7 @@ module "nomad" { | |||
| docker_contexts_bucket_name = module.buckets.envs_docker_context_bucket_name | |||
| google_service_account_key = module.init.google_service_account_key | |||
| api_docker_image_digest = module.api.api_docker_image_digest | |||
| api_secret = module.api.api_secret | |||
There was a problem hiding this comment.
api secret wasn't used (it's leftover when we were sending logs with http request to publicly accessible endpoint)
jakubno
force-pushed
the
invalidate-cache
branch
from
e5f695c to
93ab9d8
Compare
|
Is this ready to be merged in? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
There has been situation in which reseting cache would solve some problem caused by unexpected behavior (e.g. manual changes in the database), this will allow us to reset cache without any bigger disruption.