feat(jans-config-api): update schema to conform code

[yurem]

closes #9487

• I confirm that there is no impact on the docs due to the code changes in this PR.

Closes #9491,

[dryrunsecurity]

DryRun Security Summary

The pull request updates the jansNodeName attribute in the jansHealthEntry, jansLogEntry, and jansTelemetryEntry object classes, replacing the previously used jansNodeId attribute, which is not directly related to security vulnerabilities but may have implications for consistency, clarity, and potential impact on existing applications.

Expand for full summary

Summary:

The code changes in this pull request appear to be focused on updating the jansNodeName attribute in the jansHealthEntry, jansLogEntry, and jansTelemetryEntry object classes, replacing the previously used jansNodeId attribute. This change is not directly related to security vulnerabilities but is worth considering from the perspective of consistency, clarity, and potential impact on existing applications.

The use of a more descriptive attribute name, jansNodeName, can improve the understandability of the data being stored, making it easier for developers and administrators to work with the system. However, it's important to ensure that this change does not disrupt any existing applications or integrations that may have been relying on the jansNodeId attribute. Additionally, as these object classes are likely used for logging and monitoring purposes, ensuring the accuracy and consistency of the data is crucial for effective system monitoring and troubleshooting.

Files Changed:

• jans-linux-setup/jans_setup/schema/jans_schema.json: This file has been updated to replace the jansNodeId attribute with jansNodeName in the jansHealthEntry, jansLogEntry, and jansTelemetryEntry object classes. This change is not directly related to security vulnerabilities but may have implications for consistency, clarity, and potential impact on existing applications.

Code Analysis

We ran 9 analyzers against 1 file and 0 analyzers had findings. 9 analyzers had no findings.

Riskiness

🟢 Risk threshold not exceeded.

View PR in the DryRun Dashboard.

[mo-auto]

Error: Hi @yurem, You did not reference an open issue in your PR. I attempted to create an issue for you.
Please update that issues' title and body and make sure I correctly referenced it in the above PRs body.

[sonarqubecloud]

Quality Gate passed for 'jans-linux-setup'

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud