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

Backup request does not use overridden credentials #4044

Closed
cmgreen210 opened this issue Sep 23, 2019 · 1 comment · Fixed by #4047
Closed

Backup request does not use overridden credentials #4044

cmgreen210 opened this issue Sep 23, 2019 · 1 comment · Fixed by #4047
Assignees
Labels
kind/bug Something is broken. priority/P1 Serious issue that requires eventual attention (can wait a bit)

Comments

@cmgreen210
Copy link

What version of Dgraph are you using?

v1.1.0

Have you tried reproducing the issue with the latest release?

yes

What is the hardware spec (RAM, OS)?

n/a

Steps to reproduce the issue (command/config used to run Dgraph).

Set expired AWS credentials env variables (or none at all) on alpha server, then make
backup request overriding them as detailed here.

Expected behaviour and actual result.

The credentials provided in the backup request are expected to be used throughout.
Instead, if the current env credentials are stale dgraph attempts to get the latest
manifest in s3 using the old creds instead of the provided ones.

This can be seen in source here: https://github.com/dgraph-io/dgraph/blob/master/dgraph/cmd/alpha/admin_backup.go#L103

@martinmr martinmr self-assigned this Sep 23, 2019
@martinmr martinmr added kind/bug Something is broken. priority/P1 Serious issue that requires eventual attention (can wait a bit) labels Sep 23, 2019
@martinmr
Copy link
Contributor

Thanks for the detailed bug report. I've opened a PR to fix this issue for backups (more work is still needed to allow credentials to be overriden during restore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something is broken. priority/P1 Serious issue that requires eventual attention (can wait a bit)
Development

Successfully merging a pull request may close this issue.

2 participants