-
Notifications
You must be signed in to change notification settings - Fork 35
Added ca,ds and msc to the bulkUpdate mode #640
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
base: main
Are you sure you want to change the base?
Added ca,ds and msc to the bulkUpdate mode #640
Conversation
12b592d to
f04b04f
Compare
9b07304 to
6b69dcb
Compare
… so progress reporters can safely invoke them and avoid panics" This reverts commit c9ae727.
6b69dcb to
8ef9ef7
Compare
| filter: "update && plan" | ||
| filter: "update && plan && !strategy" | ||
| - name: "update strategy" | ||
| filter: "update && plan && strategy" |
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.
Oh. This escalates quickly.
Probably we could reuse one cluster and run several "updates" on it in random order.
I don't want "mock" clusters or invent fictional unit-test but bootstrapping took most of the time. Probably we could snapshot state and recreate it much faster.
| }, | ||
| } | ||
| case consts.DiscoveryType: | ||
| ytsaurus.Spec.Discovery.Image = ptr.To(testutil.YtsaurusImagePrevious) |
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.
Let's use some another reason for instance restart rather than image change.
We could treak "zero-diff" in config overrides or in instance environment.
This way we could reuse same cluster between tests.
Adding ca, ds and msc into the bulkMode. Should be rebased from main after master's PR is merged.