Skip to content

[release-20.0-rc] vtctldclient: Apply (Shard | Keyspace| Table) Routing Rules commands don't work (#16096)#16125

Merged
frouioui merged 1 commit intorelease-20.0-rcfrom
backport-16096-to-release-20.0-rc
Jun 12, 2024
Merged

[release-20.0-rc] vtctldclient: Apply (Shard | Keyspace| Table) Routing Rules commands don't work (#16096)#16125
frouioui merged 1 commit intorelease-20.0-rcfrom
backport-16096-to-release-20.0-rc

Conversation

@vitess-bot
Copy link
Copy Markdown
Contributor

@vitess-bot vitess-bot bot commented Jun 12, 2024

Description

This is a backport of #16096

…don't work (#16096)

Signed-off-by: Rohit Nayak <rohit@planetscale.com>
@vitess-bot
Copy link
Copy Markdown
Contributor Author

vitess-bot bot commented Jun 12, 2024

Review Checklist

Hello reviewers! 👋 Please follow this checklist when reviewing this Pull Request.

General

  • Ensure that the Pull Request has a descriptive title.
  • Ensure there is a link to an issue (except for internal cleanup and flaky test fixes), new features should have an RFC that documents use cases and test cases.

Tests

  • Bug fixes should have at least one unit or end-to-end test, enhancement and new features should have a sufficient number of tests.

Documentation

  • Apply the release notes (needs details) label if users need to know about this change.
  • New features should be documented.
  • There should be some code comments as to why things are implemented the way they are.
  • There should be a comment at the top of each new or modified test to explain what the test does.

New flags

  • Is this flag really necessary?
  • Flag names must be clear and intuitive, use dashes (-), and have a clear help text.

If a workflow is added or modified:

  • Each item in Jobs should be named in order to mark it as required.
  • If the workflow needs to be marked as required, the maintainer team must be notified.

Backward compatibility

  • Protobuf changes should be wire-compatible.
  • Changes to _vt tables and RPCs need to be backward compatible.
  • RPC changes should be compatible with vitess-operator
  • If a flag is removed, then it should also be removed from vitess-operator and arewefastyet, if used there.
  • vtctl command output order should be stable and awk-able.

@vitess-bot vitess-bot bot requested a review from rohit-nayak-ps June 12, 2024 05:37
@github-actions github-actions bot added this to the v20.0.0 milestone Jun 12, 2024
@codecov
Copy link
Copy Markdown

codecov bot commented Jun 12, 2024

Codecov Report

Attention: Patch coverage is 57.14286% with 3 lines in your changes missing coverage. Please review.

Project coverage is 68.24%. Comparing base (965da11) to head (3741439).

Files Patch % Lines
...cmd/vtctldclient/command/keyspace_routing_rules.go 0.00% 1 Missing ⚠️
go/cmd/vtctldclient/command/routing_rules.go 0.00% 1 Missing ⚠️
go/cmd/vtctldclient/command/shard_routing_rules.go 0.00% 1 Missing ⚠️
Additional details and impacted files
@@                 Coverage Diff                 @@
##           release-20.0-rc   #16125      +/-   ##
===================================================
+ Coverage            68.22%   68.24%   +0.01%     
===================================================
  Files                 1541     1541              
  Lines               197330   197332       +2     
===================================================
+ Hits                134626   134661      +35     
+ Misses               62704    62671      -33     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@rohit-nayak-ps rohit-nayak-ps mentioned this pull request Jun 12, 2024
49 tasks
@frouioui frouioui merged commit 087b363 into release-20.0-rc Jun 12, 2024
@frouioui frouioui deleted the backport-16096-to-release-20.0-rc branch June 12, 2024 16:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants