-
Notifications
You must be signed in to change notification settings - Fork 15
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
Provide ENSA version info to Wanda #2088
Conversation
72b2001
to
49e7361
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just two tiny thing then we can merge 🎅
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just one additional thing, sorry! And then we can merge 👍
assets/js/state/selectors/cluster.js
Outdated
@@ -62,6 +62,8 @@ export const getClusterSapSystems = createSelector( | |||
} | |||
); | |||
|
|||
export const MIXED_VERSIONS = 'MIXED_VERSIONS'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry! The value of this should be just 'mixed_versions'
, the contract that we have with the checks team is shaped like that 😅
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No worries, will revert 👌
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the CI is happy I am as well
7f72b4c
to
d9251c8
Compare
Description
This change enables the frontend to send ENSA version information about the SAP systems belonging to a certain cluster.
Business Logic
Note that the ENSA version value sent is an aggregated value of the ENSA versions present in the SAP systems for a given cluster.
If a scenario where the ENSA versions are not completely in agreement, then the value
'mixed_versions'
is sent.If the ENSA version info is not present for a SAP system, then
'mixed_versions'
is sent.Some example scenarios are below:
['ensa1']
'ensa1'
['ensa2', 'ensa2']
'ensa2'
['ensa1', 'ensa2']
'mixed_versions'
['ensa1', undefined]
'mixed_versions'
[undefined]
'mixed_versions'
How was this tested?
Added unit tests