-
Notifications
You must be signed in to change notification settings - Fork 373
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
Implement ferretdb --setup
flags
#4243
Closed
3 tasks done
Labels
area/auth
Issues about authentication and authorization
code/feature
Some user-visible feature is not implemented yet
Milestone
Comments
AlekSi
added
code/chore
Code maintenance improvements
not ready
Issues that are not ready to be worked on; PRs that should skip CI
labels
Apr 17, 2024
AlekSi
changed the title
Implement
Implement Apr 17, 2024
ferretdb --setup
CLIferretdb --setup
flags
AlekSi
removed
the
not ready
Issues that are not ready to be worked on; PRs that should skip CI
label
Apr 17, 2024
This was referenced Apr 17, 2024
Merged
9 tasks
AlekSi
added a commit
that referenced
this issue
May 30, 2024
9 tasks
AlekSi
added
code/feature
Some user-visible feature is not implemented yet
and removed
code/chore
Code maintenance improvements
labels
Jun 6, 2024
AlekSi
added a commit
that referenced
this issue
Jun 7, 2024
Closes #4243. Co-authored-by: b1ron <goldingbyron@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/auth
Issues about authentication and authorization
code/feature
Some user-visible feature is not implemented yet
What should be done?
When
--setup-username
flag is passed, FerretDB should create the specified user with the given password (that may be empty). It should not be an error if a user with that name already exists. It should do so without starting the handler but by using backends directly. It should try to establish a working backend connection up--setup-timeout
.test-enable-new-auth
's value must betrue
.Let's split the implementation into multiple PRs to make reviews easier and faster:
--test-enable-new-auth
istrue
when--setup-username
is non-empty.internal/backends
package. It should accept a backend, username, and password. Use that function in thecreateUser
command handler.Backend.Status
method andctxutil.SleepWithJitter
function.Testing should be done manually.
Where?
Definition of Done
The text was updated successfully, but these errors were encountered: