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

Update the developer guide to add a section to run remote backed storage from dev environment #16223

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

srikanthpadakanti
Copy link
Contributor

Description

Add a section to run remote backed storage from dev environment

Related Issues

#10651

Check List

  • Functionality includes testing.
  • [*] Commits are signed per the DCO using --signoff
  • [*] API changes companion pull request created, if applicable.
  • [*] Public documentation issue/PR created, if applicable.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Signed-off-by: Srikanth Padakanti <[email protected]>
@srikanthpadakanti srikanthpadakanti changed the title Update the developer guide #16096 Update the developer guide to add a section to run remote backed storage from dev environment Oct 7, 2024


// Add AWS credentials to the keystore
keystore 's3.client.default.access_key', '<access_key>'
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't think storing credentials in this file should be a recommended practice.

How about reading from env variables instead as an alternative unless there are better ways:

keystore 's3.client.default.access_key', System.getenv('AWS_ACCESS_KEY_ID')
keystore 's3.client.default.secret_key', System.getenv('AWS_SECRET_ACCESS_KEY')
keystore 's3.client.default.session_token', System.getenv('AWS_SESSION_TOKEN')
export AWS_ACCESS_KEY_ID=<access_key>
export AWS_SECRET_ACCESS_KEY=<secret_key>
export AWS_SESSION_TOKEN=<session_token>

In that way onlly authorized users are able to run this script.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants