-
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
ASCS/ERS checks #2003
ASCS/ERS checks #2003
Conversation
cibLastWritten, | ||
provider, | ||
hosts, | ||
sapSystems, | ||
details, | ||
catalog, | ||
lastExecution, | ||
onStartExecution, |
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.
Should we provide a default noop function to onStartExecution
and navigate
?
onStartExecution = () => {},
navigate = () => {},
We do that in the HanaClusterDetails component (which does not mean that is the best way, tho 😄 )
What's the way we prefer?
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.
Super! I love when things click quite seamlessly! 🚀
Just some notes:
- there is a bit of duplication between
HanaClusterDetails
,AscsErsClusterDetails
andHostDetails
when it comes to the check related action buttons and the logic they carry. Let's just be aware and ready to tackle that. - we need to also send ensa version to the catalog api call when talking about ascs/ers cluster (at least in the checks selection). A followup PR would be totally ok.
- the catalog api call needs to start using the v2 exposed by wanda. I will take care of this as part of the work related to the catalog I am addressing.
Description
Enabling checks selection and execution for ASCS/ERS clusters
How was this tested?
Unit tests added, additional stories not needed