-
Notifications
You must be signed in to change notification settings - Fork 439
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
feat(Spanner): enable drop db protection #6008
Merged
vishwarajanand
merged 4 commits into
googleapis:main
from
vishwarajanand:drop-database-protection
Jun 20, 2023
Merged
feat(Spanner): enable drop db protection #6008
vishwarajanand
merged 4 commits into
googleapis:main
from
vishwarajanand:drop-database-protection
Jun 20, 2023
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
vishwarajanand
added
the
do not merge
Indicates a pull request not ready for merge, due to either quality or timing.
label
Mar 28, 2023
rajatbhatta
reviewed
Apr 4, 2023
rajatbhatta
reviewed
Apr 4, 2023
rajatbhatta
reviewed
Apr 4, 2023
rajatbhatta
reviewed
Apr 4, 2023
By mistake, I pushed the gapic changes too. I will fix it when its time to merge this PR. |
vishwarajanand
force-pushed
the
drop-database-protection
branch
from
June 17, 2023 09:37
27f84cc
to
3be24cf
Compare
vishwarajanand
removed
the
do not merge
Indicates a pull request not ready for merge, due to either quality or timing.
label
Jun 17, 2023
vishwarajanand
force-pushed
the
drop-database-protection
branch
from
June 17, 2023 11:24
841931b
to
2fbff7c
Compare
I added a |
That’s because you also need the “breaking change allowed” label
On Sat, Jun 17, 2023 at 5:40 AM Vishwaraj Anand ***@***.***> wrote:
I added a BREAKING_CHANGE_REASON still the breaking changes check is
failing.
—
Reply to this email directly, view it on GitHub
<#6008 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAZMBJTUN67MBINFN2S6A3XLWJTPANCNFSM6AAAAAAWKUOBDE>
.
You are receiving this because your review was requested.Message ID:
***@***.***>
--
Brent Shaffer
|
yash30201
suggested changes
Jun 19, 2023
vishwarajanand
added
the
release blocking
Required feature/issue must be fixed prior to next release.
label
Jun 19, 2023
yash30201
approved these changes
Jun 20, 2023
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.
LGTM
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
api: spanner
Issues related to the Spanner API.
breaking change allowed
release blocking
Required feature/issue must be fixed prior to next release.
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.
Enables drop db feature in Spanner.
Design doc: go/drop-db-protection-spanner-php
Changes
Tests
Other tests (UT and Snippet tests pass)
Test script returns expected results:
Code to evaluate Database::updateDatabase(..)
BREAKING_CHANGE_REASON="New api added"