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

release-21.1: import: add support for non-admin outbound flag #72444

Merged
merged 1 commit into from
Nov 4, 2021

Conversation

dt
Copy link
Member

@dt dt commented Nov 4, 2021

This adds support to IMPORT for the outbound/implicit access without
admin role flag that was previously added to BACKUP, SHOW BACKUP, RESTORE,
and EXPORT in #71594.

Release note (ops change): IMPORT now also allows non-admin access to some previously admin-only URIs if --external-io-enable-non-admin-implicit-access is passed, following its prior addition to BACKUP, RESTORE, and EXPORT.

Release justification: bug fix.

This adds support to IMPORT for the outbound/implicit access without
admin role flag that was previously added to BACKUP, SHOW BACKUP, RESTORE,
and EXPORT in cockroachdb#71594.

Release note (ops change): IMPORT now also allows non-admin access to some previously admin-only URIs if --external-io-enable-non-admin-implicit-access.
@dt dt requested review from stevendanna, adityamaru and a team November 4, 2021 19:41
@cockroach-teamcity
Copy link
Member

This change is Reviewable

@dt dt changed the title import: add support for non-admin outbound flag release-21.1: import: add support for non-admin outbound flag Nov 4, 2021
@yuzefovich yuzefovich merged commit 623ac7e into cockroachdb:release-21.1 Nov 4, 2021
@dt dt deleted the no-admin-import branch November 4, 2021 22:03
@dt
Copy link
Member Author

dt commented Nov 5, 2021

Can probably ignore the release note on this one since the note on #71794 already claimed to do this, and this is just catching one case that was dropped during the backport process.

@yuzefovich
Copy link
Member

I'm confused - why does it say that I merged this? I don't remember doing that, but I did merge #72391 to 21.1 branch at about the same time 🤷

@dt
Copy link
Member Author

dt commented Nov 9, 2021

@yuzefovich I'm not sure, I clicked merge and got an error so I tried again and got a conflicts rejection which seemed to be because the commits were now on the 21.1 branch... but the PR was still shown as unmerged.

Just guessing, but I suspect some queue message is generated on commits added but got dropped, so it didn't close the PR, but then your merge's event picked it up and updated it, just with your name attached?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants