Feature/create new catalog items clear cache endpoint - #66
Conversation
| SecurityScheme securityScheme = new SecurityScheme() | ||
| .name(securitySchemeName) | ||
| SecurityScheme bearerSecurityScheme = new SecurityScheme() | ||
| .name("bearerAuth") |
There was a problem hiding this comment.
If no longer using the securitySchemeName variable you could remove it. Or use it and create anew one for basicAuth and use variables instead of hardcoded values.
| roles: PROVISIONER | ||
| roles: | ||
| - PROVISIONER | ||
| - CACHE_ADMIN |
There was a problem hiding this comment.
This should not reuse the same basic auth credentials used for the provision but instead have a separate set of credentials that are only able to delete caches. Since these credentials will be placed to bitbucket and in case they are compromised we want that they can only refresh caches, not provision anything.
|
| - basicAuth: [ ] | ||
| tags: | ||
| - CacheAdministration | ||
| summary: Refresh a cache |
There was a problem hiding this comment.
I think it clears the cache, do not get fresh values, innit?
There was a problem hiding this comment.
It does refresh de cache. Before that, we tried to use the endpoint that only clears the cache, and add a request after filter that would check if that endpoint was called to load the cache right after, but we just changed the solution approach and added a new endpoint to refresh the cache, while keeping the actuator one as default.
4 participants
No description provided.