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

Forward AWS_ACCESS_KEY_ID & AWS_SECRET_ACCESS_KEY to worker hosts #70

Open
russki opened this issue Dec 19, 2024 · 0 comments · May be fixed by #71
Open

Forward AWS_ACCESS_KEY_ID & AWS_SECRET_ACCESS_KEY to worker hosts #70

russki opened this issue Dec 19, 2024 · 0 comments · May be fixed by #71

Comments

@russki
Copy link

russki commented Dec 19, 2024

Super excited to see the support for env variables for authentication.

Would love to stop sending --s3key and --s3secret arguments in the jobs so that they're not showing up in --resfile & --csvfile files in plain text

But it doesn't seem like elbencho forwards these env variables to the worker --hosts

Is it possible to either

  • stop writing out s3key/s3secret in resfile & csvfile in plain text?
    • maybe that can be behind an optional flag

or

  • forward AWS_ACCESS_KEY_ID & AWS_SECRET_ACCESS_KEY to worker hosts automatically if they're set in the elbencho job run
@russki russki linked a pull request Dec 20, 2024 that will close this issue
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 a pull request may close this issue.

1 participant