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

Figure out S3 authentication in local Windows development #340

Open
Tracked by #312
jrhemstad opened this issue Aug 15, 2023 · 0 comments
Open
Tracked by #312

Figure out S3 authentication in local Windows development #340

jrhemstad opened this issue Aug 15, 2023 · 0 comments
Assignees

Comments

@jrhemstad
Copy link
Collaborator

jrhemstad commented Aug 15, 2023

In our Windows containers, we would like to be able to use sccache and share the same S3 bucket used by CI.

In our Linux devcontainers, this works via custom AWS/GitHub authentication logic written by @trxcllnt. These scripts can be found here: https://github.com/rapidsai/devcontainers/tree/91d2f91a2f3328cd7af39a5fcfbacc933bbaaa1b/features/src/utils/opt/devcontainer/bin/vault/s3/creds

These are currently written in bash and so will not be directly usable in Windows.

I see 3 possible options to make the AWS/S3 authentication work on Windows:

  1. Replicate the bash scripts in powershell
    • This isn't ideal as it would be redundant and the two sets of scripts would diverge over time
  2. Port the bash scripts to a language that will work in both Windows/Linux (Python? Javascript?)
    • In theory this should work?
  3. Find a way to invoke the existing bash scripts in a WSL environment on a Windows runner
    • In theory, we should be able to get the credentials in WSL and use them in the native Windows environment?
@jrhemstad jrhemstad changed the title Figure out S3 authentication in local development Figure out S3 authentication in local Windows development Aug 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Todo
Development

No branches or pull requests

2 participants