Distribute system identifier to all services #925
Assignees
Labels
architecture
enhancement
New feature or request
p2
Non-critical bugs, and features that help organizations to identify and reduce risk
size/L
High effort
Milestone
Comments
nscuro
added
enhancement
nscuro
added a commit
to DependencyTrack/hyades-apiserver
that referenced
this issue
Mar 29, 2024
This makes the cluster ID (previously system UUID) available to other instances and services. Instead of `Config.getInstance().getSystemUuid()`, `ClusterInfo.getClusterId()` must be used from now on. As the cluster ID is only generated once and then never updated, it will only be loaded upon first invocation of `ClusterInfo.getClusterId()`. Updating of the cluster ID via API or UI is prevented by marking it as read-only. Relates to DependencyTrack/hyades#925 Signed-off-by: nscuro <[email protected]>
2 tasks
nscuro
added a commit
to DependencyTrack/hyades-apiserver
that referenced
this issue
Mar 29, 2024
This makes the cluster ID (previously system UUID) available to other instances and services. Instead of `Config.getInstance().getSystemUuid()`, `ClusterInfo.getClusterId()` must be used from now on. As the cluster ID is only generated once and then never updated, it will only be loaded upon first invocation of `ClusterInfo.getClusterId()`. Updating of the cluster ID via API or UI is prevented by marking it as read-only. Relates to DependencyTrack/hyades#925 Signed-off-by: nscuro <[email protected]>
nscuro
added a commit
to DependencyTrack/hyades-apiserver
that referenced
this issue
Mar 29, 2024
This makes the cluster ID (previously system UUID) available to other instances and services. Instead of `Config.getInstance().getSystemUuid()`, `ClusterInfo.getClusterId()` must be used from now on. As the cluster ID is only generated once and then never updated, it will only be loaded upon first invocation of `ClusterInfo.getClusterId()`. Updating of the cluster ID via API or UI is prevented by marking it as read-only. Relates to DependencyTrack/hyades#925 Signed-off-by: nscuro <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Each API server instance generates a
~/.dependency-track/id.systemfile when it first starts up. The file contains a random UUID that is included in theUser-Agentheader of outgoing requests.Now, with multiple services and service instances, storing this identifier on disk does not work anymore. Instead, it needs to be distributed to all services that are part of the system.
Storing it in the database is an option, however not all services have or require a database connection at the moment (e.g. mirror service doesn't). Perhaps there is a way to distribute the identifier via Kafka topic instead.
The text was updated successfully, but these errors were encountered: