-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE]: Capture more details during cluster assessment to provide deeper insights into impact analysis #1155
Comments
@dmoore247 this issue is not concrete enough - it cannot be distributed among people without context. Please split this issue up to a more granular ones and provide extremely detailed input. |
@vsevolodstep-db can you take a look at this issue, as it seems to align with your team's priorities |
place it in the same shared state that currently tracked database is. Also parse the |
No longer necessary |
Is there an existing issue for this?
Problem statement
The
$inventory.clusters
table contains just ~6 fields of information while the cluster contains dozens of attributes.Determining code compatibility depends on knowing more about the current compute cluster. If the code is already running on a UC (shared) compute platform, if is already running as a single user compute or job compute then the code block from the audit log can be dropped from
interactive
assessment dashboard.For example:
data_security_mode
will help eliminate false positives for clusters already converted or are of a Assigned type of clusterProposed Solution
Adopt a "touch it, take it" approach when scanning clusters to satisfy future refinements to the assessment processes. (e.g. upgrade all clusters tagged with a certain department, group the assessment by a cluster tag to capture a group of workloads by business units)
Retain the existing
$inventory.clusters
table structure and columns for backwards compatibility.Add an additional field into
$inventory.clusters
table, calledattributes
.Within this table store the complex json obtained from the clusters api get method.
Ensure the
attributes
field can be queried using the SQL json notation for ease of use.Additional Context
No response
The text was updated successfully, but these errors were encountered: