-
Notifications
You must be signed in to change notification settings - Fork 145
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
Generate S3 server credentials on-the-fly #3114
Conversation
ca47019
to
cdf9ae5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
apart from the math/rand => crypto/rand transition this looks fine to me. I'd like @pjbgf to have a look, too.
b9e3065
to
cb2ffcc
Compare
cb2ffcc
to
dab0e6c
Compare
e7049f6
to
ff16ce9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's make sure to squash the commits before merging
1c982a1
to
1998cd8
Compare
e4083d0
to
5eee0ae
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
To improve the security of GitOps Run we now generate access and secret keys each time the `gitops beta run` command is run. These credentials are passed on to the S3 server and used in the client code for authentication.
5eee0ae
to
75268c4
Compare
Changes:
To improve the security of GitOps Run we now generate access and secret keys each time the
gitops beta run
command is run. These credentials are passed on to the S3 server and used in the client code for authentication.