Document the steps required to rebuild the dashboard cache

[abstractj]

Description

There is currently no documentation on how to rebuild the cache for the security dashboard. When the dashboard needs to be refreshed, there's no runbook to follow, we don't know the exact steps, who has access, or what the expected outcome looks like.

Goals

• Document the step-by-step process to rebuild or refresh the cache
• Note any required access, credentials, or permissions
• Add the runbook somewhere the team can find it

Non-goals

• Changing how the cache works
• Automating the rebuild (that can come later once we understand the process)

[abstractj]

@stianst assigned to you, because you are the only one who knows about it.

[stianst]

@abstractj re-build the cache? or update the cache? updating the cache is done with https://github.com/keycloak/dashboard/actions/workflows/data.yml and you can select what areas to update. There's some stuff in there that can force reloading some parts, I can extend that to include a checkbox on the action to force a reload rather than an update

[abstractj]

@stianst I don't think we need to go that far (considering other priorities), only instructions on how to manually trigger the dashboard update into the dashboard in a README file should be enough. That won't happen too often, but being able to do that before our weekly meeting is helpful.