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

Be able to set BINARY_DOWNLOAD_PREFIX used in install.sh #1895

Open
mikeq opened this issue Apr 30, 2024 · 2 comments
Open

Be able to set BINARY_DOWNLOAD_PREFIX used in install.sh #1895

mikeq opened this issue Apr 30, 2024 · 2 comments
Labels
feature 🎉 new commands, flags, functionality, and improved error messages triage issues and PRs that need to be triaged

Comments

@mikeq
Copy link

mikeq commented Apr 30, 2024

Description

Our CI/CD pipelines do not have access to the outside world directly but through our Nexus Repo manager. The rover installation using the shell script has a hard coded value for the BINARY_DOWNLOAD_PREFIX, ideally this should pick up an environment variable if specified or default to the hardcoded value.

BINARY_DOWNLOAD_PREFIX=${BINARY_DOWNLOAD_PREFIX:-"https://github.com/apollographql/rover/releases/download"}

This would allow us to point BINARY_DOWNLOAD_PREFIX to our internal Nexus repo to fetch the rover release

This issue refers to https://github.com/apollographql/rover/blob/main/installers/binstall/scripts/nix/install.sh

@mikeq mikeq added feature 🎉 new commands, flags, functionality, and improved error messages triage issues and PRs that need to be triaged labels Apr 30, 2024
@dylan-apollo
Copy link
Member

Most of the install script is about checking for dependencies and architecture. As a workaround, you could instead download the binary from your internal repo and run it directly (or add it to path manually).

@mikeq
Copy link
Author

mikeq commented May 2, 2024

@dylan-apollo yeah, as a workaround I have copied the install.sh and made the change I suggest above to line 18 until this request is actioned. The script does an environment check for $VERSION being passed in and this is much the same.

It is better to have a script workout which binary I need, which will vary depending on what container I run it within or the build arguments passed to the CI pipeline.

I'm happy to submit a PR for it, but I believe that needs to be agreed in advance?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature 🎉 new commands, flags, functionality, and improved error messages triage issues and PRs that need to be triaged
Projects
None yet
Development

No branches or pull requests

2 participants