Skip to content

tidb: fix placement doc (#7073)#7095

Closed
ti-chi-bot wants to merge 1 commit into
pingcap:release-4.0from
ti-chi-bot:cherry-pick-7073-to-release-4.0
Closed

tidb: fix placement doc (#7073)#7095
ti-chi-bot wants to merge 1 commit into
pingcap:release-4.0from
ti-chi-bot:cherry-pick-7073-to-release-4.0

Conversation

@ti-chi-bot
Copy link
Copy Markdown
Member

This is an automated cherry-pick of #7073

First-time contributors' checklist

What is changed, added or deleted? (Required)

fix the wrong placement command, since the usage like that:

Usage:
  pd-ctl config placement-rules rule-bundle save [flags]

Flags:
  -h, --help        help for save
      --in string   the file contains all group configs and all rules (default "rules.json")
      --partial     do not drop all old configurations, partial update

unknown shorthand flag: 'i' in -in=rules.json

Which TiDB version(s) do your changes apply to? (Required)

Tips for choosing the affected version(s):

By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.

For details, see tips for choosing the affected versions (in Chinese).

  • master (the latest development version)
  • v5.2 (TiDB 5.2 versions)
  • v5.1 (TiDB 5.1 versions)
  • v5.0 (TiDB 5.0 versions)
  • v4.0 (TiDB 4.0 versions)
  • v3.1 (TiDB 3.1 versions)
  • v3.0 (TiDB 3.0 versions)
  • v2.1 (TiDB 2.1 versions)

What is the related PR or file link(s)?

  • This PR is translated from:
  • Other reference link(s):

Do your changes match any of the following descriptions?

  • Delete files
  • Change aliases
  • Need modification after applied to another branch
  • Might cause conflicts after applied to another branch

Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
@ti-chi-bot
Copy link
Copy Markdown
Member Author

[REVIEW NOTIFICATION]

This pull request has not been approved.

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.

Details

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 contribution This PR is from a community contributor. first-time-contributor Indicates that the PR was contributed by an external member and is a first-time contributor. labels Sep 10, 2021
@ti-chi-bot ti-chi-bot mentioned this pull request Sep 10, 2021
13 tasks
@ti-chi-bot ti-chi-bot added sig/docs Indicates that the Issue or PR belongs to the docs SIG. area/scheduling Indicates that the Issue or PR belongs to the area of scheduling. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. type/bugfix This PR fixes a bug. type/cherry-pick-for-release-4.0 This PR is cherry-picked to release-4.0 from a source PR. labels Sep 10, 2021
@ti-chi-bot ti-chi-bot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Sep 10, 2021
@TomShawn
Copy link
Copy Markdown
Contributor

This branch does not need cherry-pick.

@TomShawn TomShawn closed this Sep 10, 2021
@TomShawn TomShawn removed contribution This PR is from a community contributor. type/bugfix This PR fixes a bug. type/cherry-pick-for-release-4.0 This PR is cherry-picked to release-4.0 from a source PR. first-time-contributor Indicates that the PR was contributed by an external member and is a first-time contributor. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. area/scheduling Indicates that the Issue or PR belongs to the area of scheduling. sig/docs Indicates that the Issue or PR belongs to the docs SIG. labels Sep 10, 2021
@ti-chi-bot ti-chi-bot added the missing-translation-status This PR does not have translation status info. label Sep 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

missing-translation-status This PR does not have translation status info.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants