-
Notifications
You must be signed in to change notification settings - Fork 167
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
feat: new cluster topology and component version API #6582
Conversation
…ology' into feature/cluster-topology
} | ||
|
||
if !validate(topology.Orders.StartupOrder) { | ||
return fmt.Errorf("the components in startup order are different from those from definition") |
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.
There's a question here: according to this validation rule, the components defined in StartupOrder/ShutdownOrder/UpdateOrder must completely cover topology.Components. Is this expected? What if the user only expects some of the components to have dependencies?
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.
Yes, the expected behavior is to either specify no components or all components, this is the simplest and most accurate strategy.
0f1f4b0
to
cab0202
Compare
/approve |
No description provided.