-
Notifications
You must be signed in to change notification settings - Fork 592
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
rpk: make mechanism flag required in user update #21452
Conversation
new failures in https://buildkite.com/redpanda/redpanda/builds/51612#0190be5d-4556-4861-ac06-fd2aef2a9710:
new failures in https://buildkite.com/redpanda/redpanda/builds/51612#0190be5d-4551-4e07-8528-c460a31a8dfd:
new failures in https://buildkite.com/redpanda/redpanda/builds/51612#0190be5e-f787-4745-9365-7aa38c04d8af:
|
ducktape was retried in https://buildkite.com/redpanda/redpanda/builds/51612#0190be5d-4554-4b73-b5a3-e82a80669eb8 ducktape was retried in https://buildkite.com/redpanda/redpanda/builds/51612#0190be5d-4551-4e07-8528-c460a31a8dfd |
Without this, a user could inadvertently change the mechanism because we default the flag to SCRAM-SHA-256.
93908e0
to
07943e6
Compare
Force Push: update Ducktape test with the new flag |
Unrelated timeout in rp unit test: https://buildkite.com/redpanda/redpanda/builds/51661#0190c152-5853-420f-9edc-a56ad06124f1/6-11162 is #18563 |
/backport v24.1.x |
/backport v23.3.x |
/backport v23.2.x |
/backport v24.1.x |
/backport v23.3.x |
/backport v23.2.x |
Without this, a user could inadvertently change the mechanism because we default the flag to
SCRAM-SHA-256.
Backports Required
Release Notes
Improvements
rpk security user update
.