CRAYSAT-1929: Fix CFS fields in sat status
for CFS v3
#279
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.
Summary and Scope
The
CFSStatusModule
still had hard-coded property names for the properties of a CFS component, and these property names were only valid for CFS v2, sosat status
only showed CFS fields when CFS v2 was used. Update the mapping so that it correctly maps CFS properties to thesat status
column names for both CFS v2 and v3.Issues and Related PRs
Testing
Tested on:
Test description:
Built
cray-sat
image and tested onnoname
with both CFS versions, that is:sat status --cfs-version v2
sat status --cfs-version v3
Risks and Mitigations
Low risk change which only affects
sat status
.Pull Request Checklist