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

Add Regenerate S3 Credentials for OBC to the CLI #857

Merged
merged 1 commit into from Mar 8, 2022

Conversation

liranmauda
Copy link
Contributor

Explain the changes

  • Add Regenerate S3 Credentials for OBC to the CLI
  • Fixed the RPC call for list accounts

Signed-off-by: liranmauda liran.mauda@gmail.com

Testing Instructions:

  1. Regenerate OBC credentials
  2. See that s3 ops are working with the new credentials

pkg/obc/obc.go Outdated Show resolved Hide resolved
pkg/obc/obc.go Outdated Show resolved Hide resolved
pkg/nb/api.go Outdated Show resolved Hide resolved
pkg/obc/obc.go Outdated Show resolved Hide resolved
secret.StringData["AWS_SECRET_ACCESS_KEY"] = accessKeys.SecretKey

//If we will not be able to update the secret we will print the credentials as they allready been changed by the RPC
if !util.KubeUpdate(secret) {
Copy link
Contributor

Choose a reason for hiding this comment

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

@liranmauda @dannyzaken can we handle this situation better? maybe somehow hang the failure on the OBC/OB or somehow get the bucket into a rejected state and ask the user to regenerate again?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

At this point, the account credentials are already changed and we are failing to update the secret.
The apps that are using this secret will also disconnect, and as we cant revert the best way to work around it is to regenerate again, and unless there is a fundamental issue with the secret that prevents us from updating it, it will fix it.
as a middle solution, we just print the new credentials (which can be manually edited into the secret as b64, by us/support/user).

@dannyzaken @romayalon

@liranmauda liranmauda force-pushed the liran-add-regenerate-keys-obc branch 4 times, most recently from bfbc716 to 05a630e Compare March 6, 2022 12:48
@liranmauda liranmauda force-pushed the liran-add-regenerate-keys-obc branch from 05a630e to 16f6c55 Compare March 8, 2022 10:45
- Add Regenerate S3 Credentials for OBC to the CLI

Signed-off-by: liranmauda <liran.mauda@gmail.com>
@liranmauda liranmauda force-pushed the liran-add-regenerate-keys-obc branch from 16f6c55 to 73527a9 Compare March 8, 2022 11:29
@liranmauda liranmauda merged commit 44c3e7e into noobaa:master Mar 8, 2022
12 checks passed
@liranmauda liranmauda deleted the liran-add-regenerate-keys-obc branch July 23, 2023 08:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants