File map storage: Entities changing their ID (example: clientId change)

[ahus1]

Description

For some entities, the file store uses the name humans refer to them as a file name and as a reference in the YAML files. One of these examples is the clientId.

When the user changes the clientId in the UI, the current implementation updates the clientId in the YAML file, but doesn't yet change the name of the file. In addition to that, all the references to that client in the file store need updating, for example the client roles (at the time of writing, they are stored in a folder with the clientId, and they also store the clientId in their YAML).

Discussion

Current behavior:

• Create a client with the UI (and save)
• Create a client role (and save)
• Rename the clientId (and save)
• Go to the list of clients -> client appears with the the new clientId
• Pick the new client from the list -> client not found, as the file on disk hasn't been renamed

Expected behavior:

• After renaming a clientId, the client should be pickable from the list of clients, and the client roles should still be visible.

Similar problems might appear for other entities.

Motivation

The file store uses for entities humans refer to a derived ID from a descriptive name of the entity. When that name changes, and therefore its ID, all references need to change.

Details

No response

[hmlnarik]

This issue is akin source refactoring (e.g. rename class), with additional complexity of maintaining the state across potentially multiple stores in tree store.

It may be developed for special cases in the future, but at this moment, changing ID will not be supported in the file store.