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

Document replacing credentials in a basic auth setup #8491

Merged
merged 3 commits into from
Jan 14, 2025

Conversation

yonipeleg33
Copy link
Contributor

Closes #8444

@yonipeleg33 yonipeleg33 added docs Improvements or additions to documentation include-changelog PR description should be included in next release changelog labels Jan 13, 2025
Copy link

github-actions bot commented Jan 13, 2025

♻️ PR Preview 2dc6a56 has been successfully destroyed since this PR has been closed.

🤖 By surge-preview

Copy link

E2E Test Results - DynamoDB Local - Local Block Adapter

13 passed

Copy link

E2E Test Results - Quickstart

11 passed

Copy link
Contributor

@Isan-Rivkin Isan-Rivkin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added non blocking comments, LGTM

@@ -25,6 +25,34 @@ Existing lakeFS installations that have a single user and a single set of creden
Installations that have more than one user / credentials will require to run a command and choose which set of user + credentials to migrate
(more details [here](#migration-of-existing-user))

### Replacing credentials

To replace the credentials of the (single) user in a lakefs installation:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
To replace the credentials of the (single) user in a lakefs installation:
In non-ACL setup (single user) to replace the credentials in a lakefs installation:

Comment on lines 49 to 52
> Calling the `superuser` command with `--access-key-id` and without `--secret-access-key` will make lakefs try to
> import an existing user (see [Migration of existing user](#migration-of-existing-user)).
> In case you already deleted the user by following step (1), this import operation will **fail** and result in an
> **unrecoverable** state, and a clean installation is the only way out.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
> Calling the `superuser` command with `--access-key-id` and without `--secret-access-key` will make lakefs try to
> import an existing user (see [Migration of existing user](#migration-of-existing-user)).
> In case you already deleted the user by following step (1), this import operation will **fail** and result in an
> **unrecoverable** state, and a clean installation is the only way out.
> Calling the `superuser` command with pre-defined `--access-key-id` and `--secret-access-key` is possible but should be done with caution. Make sure that `--secret-access-key` is **not empty**, It's suitable for ACL's
> import an existing user (see [Migration of existing user](#migration-of-existing-user)).
> In case you already deleted the user by following step (1), this import operation will **fail** and result in an
> **unrecoverable** state, and a clean installation is the only way out.

> In case you already deleted the user by following step (1), this import operation will **fail** and result in an
> **unrecoverable** state, and a clean installation is the only way out.
>
> In general, replacing credentials is a risky operation. Proceed with caution.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure what is the value of this sentence, I would remove it (up to you)

Copy link
Contributor Author

@yonipeleg33 yonipeleg33 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @Isan-Rivkin, I changed the wording in the "direction" of your suggestions, but not exactly (preferred other sentence structures).
You're welcome to take another look (not asking for re-review though 🙂)

Copy link
Contributor

@talSofer talSofer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for documenting this!
In the current docs structure, this is the best place for this but we may want to change this is the future (a product item).

@@ -25,6 +25,34 @@ Existing lakeFS installations that have a single user and a single set of creden
Installations that have more than one user / credentials will require to run a command and choose which set of user + credentials to migrate
(more details [here](#migration-of-existing-user))

### Replacing credentials

In non-ACL setup (single user), replacing credentials can be done as follows:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
In non-ACL setup (single user), replacing credentials can be done as follows:
In a single user setup, replacing credentials can be done as follows:

@@ -25,6 +25,34 @@ Existing lakeFS installations that have a single user and a single set of creden
Installations that have more than one user / credentials will require to run a command and choose which set of user + credentials to migrate
(more details [here](#migration-of-existing-user))

### Replacing credentials
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Credentials Replacement

Copy link
Contributor Author

@yonipeleg33 yonipeleg33 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @talSofer, fixed your comments.
Waiting for CI and pulling

@yonipeleg33 yonipeleg33 enabled auto-merge (squash) January 14, 2025 13:08
@yonipeleg33 yonipeleg33 merged commit 9c9be9d into master Jan 14, 2025
39 checks passed
@yonipeleg33 yonipeleg33 deleted the document-auth-replace-keys branch January 14, 2025 13:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Improvements or additions to documentation include-changelog PR description should be included in next release changelog
Projects
None yet
Development

Successfully merging this pull request may close these issues.

OSS Admin - rotate credentials
3 participants