-
Notifications
You must be signed in to change notification settings - Fork 48
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
Add ForceMove option on vacate parameters #489
base: master
Are you sure you want to change the base?
Changes from 5 commits
ba19c5b
5ea6794
799ce06
7d3cc67
9a53596
d8b9dc8
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -127,6 +127,7 @@ func moveNodes(id string, params *VacateParams, p *pool.Pool) ([]pool.Validator, | |
WithAllocatorID(id). | ||
WithMoveOnly(params.MoveOnly). | ||
WithContext(api.WithRegion(context.Background(), params.Region)). | ||
WithForceMove(params.ForceMove). | ||
WithValidateOnly(ec.Bool(true)), | ||
params.AuthWriter, | ||
) | ||
|
@@ -282,6 +283,7 @@ func newVacateClusterParams(params addAllocatorMovesToPoolParams, id, kind strin | |
Output: params.VacateParams.Output, | ||
OutputFormat: params.VacateParams.OutputFormat, | ||
MoveOnly: params.VacateParams.MoveOnly, | ||
ForceMove: params.VacateParams.ForceMove, | ||
PlanOverrides: params.VacateParams.PlanOverrides, | ||
} | ||
|
||
|
@@ -391,6 +393,7 @@ func newMoveClusterParams(params *VacateClusterParams) (*platform_infrastructure | |
platform_infrastructure.NewMoveClustersParams(). | ||
WithAllocatorDown(params.AllocatorDown). | ||
WithMoveOnly(params.MoveOnly). | ||
WithForceMove(params.ForceMove). | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is this needed here? I would remove it because I think it alters the soteria behaviour i.e. currently we:
Now, if we set the force_move flag in the validation API, the admin console will respect what u asked. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. If I remove this one, This is the result ( see logs https://platform-logging.kb.eu-west-1.aws.qa.cld.elstc.co/app/r/s/1ElD8 ) Testing with The first one will have the correct value
The second and the third one will have the wrong value
Testing with all the logs entries will have |
||
WithAllocatorID(params.ID). | ||
WithContext(api.WithRegion(context.Background(), params.Region)). | ||
WithValidateOnly(ec.Bool(true)). | ||
|
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.
Same here, won't this alter the behaviour of the soteria flow? for example to always set
force_move
to true?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 I remove this one, This is the result ( see logs https://platform-logging.kb.eu-west-1.aws.qa.cld.elstc.co/app/r/s/g99SA )
Force_move: true
in Fleetctl code:Our of 3 log entries,
The first one will have the wong value
forceMove=[false]
:The second and the third one will have the correct value
forceMove=[true]
:Force_move: true
in Fleetctl code:all the logs entries will have
forceMove=[false]
see see logs https://platform-logging.kb.eu-west-1.aws.qa.cld.elstc.co/app/r/s/se28H