*: unify ansible names #2108
Merged
*: unify ansible names #2108
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
TomShawn
added
type/bug-fix
TomShawn
added
translation/done
TomShawn
added
type/enhancement
sre-bot
pushed a commit
to sre-bot/docs
that referenced
this pull request
Mar 27, 2020
Signed-off-by: sre-bot <sre-bot@pingcap.com>
4 tasks
|
cherry pick to release-3.0 in PR #2112 |
sre-bot
pushed a commit
to sre-bot/docs
that referenced
this pull request
Mar 27, 2020
Signed-off-by: sre-bot <sre-bot@pingcap.com>
4 tasks
|
cherry pick to release-3.1 in PR #2113 |
sre-bot
added a commit
that referenced
this pull request
Mar 27, 2020
sre-bot
added a commit
that referenced
this pull request
Mar 27, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is changed, added or deleted? (Required)
Change
AnsibletoTiDB AnsibleorDM-Ansiblein proper places.v2.1 is updated in #2110 to avoid excessive conflicts.
Which TiDB version(s) do your changes apply to? (Required)
If you select two or more versions from above, to trigger the bot to cherry-pick this PR to your desired release version branch(es), you must add corresponding labels such as needs-cherry-pick-3.1, needs-cherry-pick-3.0, and needs-cherry-pick-2.1.
What is the related PR or file link(s)?