I'm using the pants_bin_name option to point Pants to ./pants-bin. I've created my own pants script, which does two things:
- Refreshes a token to access our private CodeArtifact Python package index.
- Calls
pants-bin, passing in all arguments that were provided to the pants script.
This allows us to keep CodeArtifact authenticated and use Pants in the standard way.
Right now I don't think the init-pants GitHub Action respects pants_bin_name option, and instead looks directly in ./pants, which prevents us from using the latest version of this GitHub Action. (I might be wrong here, I'm pretty new to Pants)
Does it make sense to change the behaviour of this GitHub Action to check what pants_bin_name is (or perhaps the version of Pants), instead of having a look inside the pants script itself? If there is a recommended approach, I'm quite happy to attempt this change myself!
I'm using the
pants_bin_nameoption to point Pants to./pants-bin. I've created my ownpantsscript, which does two things:pants-bin, passing in all arguments that were provided to thepantsscript.This allows us to keep CodeArtifact authenticated and use Pants in the standard way.
Right now I don't think the
init-pantsGitHub Action respectspants_bin_nameoption, and instead looks directly in./pants, which prevents us from using the latest version of this GitHub Action. (I might be wrong here, I'm pretty new to Pants)Does it make sense to change the behaviour of this GitHub Action to check what
pants_bin_nameis (or perhaps the version of Pants), instead of having a look inside thepantsscript itself? If there is a recommended approach, I'm quite happy to attempt this change myself!