Is your feature request related to a problem? Please describe.
When building wheels using GitHub actions, I need to support a different way of accessing the secret snopt code. As of today, the builder assumes that git credentials are available directly. This ends up being a struggle to provide as part of GitHub actions.
Describe the solution you'd like
When running bazel run //tools/wheel:builder, there should be an option to configure SNOPT_PATH to point to a file. This is the current work-around I'm using:
Instead of hard-coding that with a patch file, I'd like to pass a flag on the command line.
Note that this flag only needs to work when --no-provision is in effect. There is no need to add logic to copy the SNOPT_PATH file from outside to inside of Docker. (However, if it makes it easier to test locally by support the docker-aware file copying as part of this work, that's fine too.)
Is your feature request related to a problem? Please describe.
When building wheels using GitHub actions, I need to support a different way of accessing the secret snopt code. As of today, the builder assumes that
git
credentials are available directly. This ends up being a struggle to provide as part of GitHub actions.Describe the solution you'd like
When running
bazel run //tools/wheel:builder
, there should be an option to configureSNOPT_PATH
to point to a file. This is the current work-around I'm using:Instead of hard-coding that with a patch file, I'd like to pass a flag on the command line.
Note that this flag only needs to work when
--no-provision
is in effect. There is no need to add logic to copy theSNOPT_PATH
file from outside to inside of Docker. (However, if it makes it easier to test locally by support the docker-aware file copying as part of this work, that's fine too.)