Skip to content
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

cluster: fix can't skip confirmation of scale-out #1645

Merged
merged 6 commits into from
Dec 2, 2021

Conversation

srstack
Copy link
Collaborator

@srstack srstack commented Dec 1, 2021

What problem does this PR solve?

close #1640

What is changed and how it works?

fix can't skip confirmation of scale-out

Check List

Tests

  • Manual test (add detailed scripts or steps below)
 ./tiup-cluster scale-out cluster-name scale-out.yaml --yes
 ./tiup-cluster scale-out cluster-name scale-out.yaml --stage1 --yes
 ./tiup-cluster scale-out cluster-name scale-out.yaml --stage2 --yes

Code changes

  • Has exported variable/fields change

Side effects

Related changes

Release notes:

NONE

@srstack srstack self-assigned this Dec 1, 2021
@ti-chi-bot
Copy link
Member

ti-chi-bot commented Dec 1, 2021

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • AstroProfundis

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

@ti-chi-bot ti-chi-bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Dec 1, 2021
@codecov-commenter
Copy link

codecov-commenter commented Dec 1, 2021

Codecov Report

Merging #1645 (930a426) into master (c6b2e51) will increase coverage by 34.83%.
The diff coverage is 15.38%.

Impacted file tree graph

@@             Coverage Diff             @@
##           master    #1645       +/-   ##
===========================================
+ Coverage   15.58%   50.41%   +34.83%     
===========================================
  Files         151      294      +143     
  Lines       15250    26981    +11731     
===========================================
+ Hits         2376    13603    +11227     
+ Misses      12357    11310     -1047     
- Partials      517     2068     +1551     
Flag Coverage Δ
cluster 43.82% <15.38%> (?)
dm 25.87% <15.38%> (?)
integrate 50.41% <15.38%> (+34.83%) ⬆️
playground 13.33% <ø> (?)
tiup 15.58% <ø> (ø)
unittest ∅ <ø> (∅)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
pkg/cluster/manager/scale_out.go 36.05% <15.38%> (ø)
components/cluster/command/reload.go 80.64% <0.00%> (ø)
pkg/cluster/manager/manager.go 77.41% <0.00%> (ø)
pkg/cluster/task/sysctl.go 68.42% <0.00%> (ø)
components/cluster/command/enable.go 75.00% <0.00%> (ø)
components/dm/command/destroy.go 63.15% <0.00%> (ø)
pkg/cluster/task/update_meta.go 85.00% <0.00%> (ø)
pkg/cluster/ansible/service.go 0.00% <0.00%> (ø)
pkg/cluster/task/copy_file.go 57.14% <0.00%> (ø)
... and 237 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c6b2e51...930a426. Read the comment docs.

@onlyacat
Copy link
Contributor

onlyacat commented Dec 1, 2021

I guess it might be more user-friendly to print the warning while skipping the confirmation? So that the users know what happens during the procedure.

@srstack
Copy link
Collaborator Author

srstack commented Dec 1, 2021

I guess it might be more user-friendly to print the warning while skipping the confirmation? So that the users know what happens during the procedure.

yes~ I am going to fix it

@ti-chi-bot ti-chi-bot added the status/LGT1 Indicates that a PR has LGTM 1. label Dec 2, 2021
@AstroProfundis
Copy link
Contributor

/merge

@ti-chi-bot
Copy link
Member

This pull request has been accepted and is ready to merge.

Commit hash: 930a426

@ti-chi-bot ti-chi-bot added the status/can-merge Indicates a PR has been approved by a committer. label Dec 2, 2021
@ti-chi-bot ti-chi-bot merged commit 5e97222 into pingcap:master Dec 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
size/M Denotes a PR that changes 30-99 lines, ignoring generated files. status/can-merge Indicates a PR has been approved by a committer. status/LGT1 Indicates that a PR has LGTM 1.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

--yes can't skip confirmation of scale-out
5 participants