Detect Configuration Drift Compare to Baseline#1969
Closed
chetnadev wants to merge 3 commits intoServiceNowDevProgram:mainfrom
Closed
Detect Configuration Drift Compare to Baseline#1969chetnadev wants to merge 3 commits intoServiceNowDevProgram:mainfrom
chetnadev wants to merge 3 commits intoServiceNowDevProgram:mainfrom
Conversation
Contributor
|
@chetnadev did you get a chance to look at the comments above? |
Contributor
|
Hi @chetnadev Closing this for now. Once you make additional changes as suggested, feel free to re-open this Pull Request or create a new one. |
Contributor
Author
|
Hi @rohi-v I don't see any comments/ changes here mentioned by you |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This business rule detects if a CI's configuration has drifted from its baseline by checking key attributes (RAM, CPU, OS). If differences are found:
The drift is logged in a custom log table.
An event is triggered for further action.
Gets the latest baseline for the current CI.
Compares key fields (ram, cpu_count, os) between the current CI and the baseline.
If differences (a "drift") are found:
It logs the drift in a custom table (u_drift_log).
It triggers an event (ci.drift_detected) to possibly notify or take further action.