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

feat: change binary download url #5369

Merged
merged 1 commit into from
Aug 16, 2024
Merged

feat: change binary download url #5369

merged 1 commit into from
Aug 16, 2024

Conversation

sandor-trombitas
Copy link
Contributor

@sandor-trombitas sandor-trombitas commented Jul 19, 2024

Pull Request Submission

Please check the boxes once done.

The pull request must:

  • Reviewer Documentation
    • follow CONTRIBUTING rules
    • be accompanied by a detailed description of the changes
    • contain a risk assessment of the change (Low | Medium | High) with regards to breaking existing functionality. A change e.g. of an underlying language plugin can completely break the functionality for that language, but appearing as only a version change in the dependencies.
    • highlight breaking API if applicable
    • contain a link to the automatic tests that cover the updated functionality.
    • contain testing instructions in case that the reviewer wants to manual verify as well, to add to the manual testing done by the author.
    • link to the link to the PR for the User-facing documentation
  • User facing Documentation
    • update any relevant documentation in gitbook by submitting a gitbook PR, and including the PR link here
    • ensure that the message of the final single commit is descriptive and prefixed with either feat: or fix: , others might be used in rare occasions as well, if there is no need to document the changes in the release notes. The changes or fixes should be described in detail in the commit message for the changelog & release notes.
  • Testing
    • Changes, removals and additions to functionality must be covered by acceptance / integration tests or smoke tests - either already existing ones, or new ones, created by the author of the PR.

Pull Request Review

All pull requests must undergo a thorough review process before being merged.
The review process of the code PR should include code review, testing, and any necessary feedback or revisions.
Pull request reviews of functionality developed in other teams only review the given documentation and test reports.

Manual testing will not be performed by the reviewing team, and is the responsibility of the author of the PR.

For Node projects: It’s important to make sure changes in package.json are also affecting package-lock.json correctly.

If a dependency is not necessary, don’t add it.

When adding a new package as a dependency, make sure that the change is absolutely necessary. We would like to refrain from adding new dependencies when possible.
Documentation PRs in gitbook are reviewed by Snyk's content team. They will also advise on the best phrasing and structuring if needed.

Pull Request Approval

Once a pull request has been reviewed and all necessary revisions have been made, it is approved for merging into
the main codebase. The merging of the code PR is performed by the code owners, the merging of the documentation PR
by our content writers.

What does this PR do?

This changes the the download url for our ts-binary-wrapper. When people will install snyk-cli via npm, they will download the binary from downloads.snyk.io, if this url fails, the script will try to download it from static.snyk.io

Where should the reviewer start?

ts-binary-wrapper/src/common.ts
ts-binary-wrapper/src/bootstrap.ts

How should this be manually tested?

cd ts-binary-wrapper
npm ci --ignore-scripts
npm run build
npx ts-node ./test/util/prepareEnvironment.ts exec
mv ./test/util/something/generated/sha256sums.txt ./wrapper_dist/generated/sha256sums.txt
mv ./test/util/something/generated/version wrapper_dist/generated/version
npm run postinstall

Any background context you want to provide?

What are the relevant tickets?

Screenshots

Additional questions

Copy link
Contributor

github-actions bot commented Jul 19, 2024

Warnings
⚠️

Since the CLI is unifying on a standard and improved tooling, we're starting to migrate old-style imports and exports to ES6 ones.
A file you've modified is using either module.exports or require(). If you can, please update them to ES6 import syntax and export syntax.
Files found:

  • ts-binary-wrapper/src/common.ts

Generated by 🚫 dangerJS against 89546b0

Comment on lines 52 to 61
public getDownloadLocation(): string {
const baseUrl = 'https://static.snyk.io/cli/v';
return baseUrl + this.version + '/' + this.binaryName;
const baseUrl = 'https://downloads.snyk.io/cli';

return this.buildDownloadUrl(baseUrl);
}

public getBackupDownloadLocation(): string {
const baseUrl = 'https://static.snyk.io/cli';

return this.buildDownloadUrl(baseUrl);
Copy link
Contributor

@j-luong j-luong Jul 23, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

question: would

public getDownloadLocation(baseUrl = 'https://downloads.snyk.io/cli'): string {
    return baseUrl + this.version + '/' + this.binaryName;
  }

be cleaner? getDownloadLocation() and getBackupDownloadLocation() are more or less identical and we could get rid of buildDownloadUrl() if we just update getDownloadLocation()

@sandor-trombitas sandor-trombitas changed the title feat[deploy]: change binary download url feat: change binary download url Jul 23, 2024
@@ -242,7 +253,7 @@ export function downloadExecutable(
filenameShasum: string,
): Promise<Error | undefined> {
return new Promise<Error | undefined>(function(resolve) {
const options = new URL(downloadUrl);
const options = new URL(downloadUrl + '?utm_source=npm');
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Praise! Happy to see this :)

Copy link
Collaborator

@PeterSchafer PeterSchafer Jul 23, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion: let's change the utm_source to this something like TS_BINARY_WRAPPER to be more future proof and align with integration names.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion 2: Let's also use the chance to add the missing env variables SNYK_INTEGRATION_NAME, SNYK_INTEGRATION_VERSION to runWrapper() the integration name would also be TS_BINARY_WRAPPER for consistency.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've added the integration name and version as env vars, let me know what you think

return this.buildDownloadUrl(baseUrl);
}

public getBackupDownloadLocation(): string {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Question: Would make the logic easier and more consistent if we change getDownloadLocation() to return a list of URLs?
This list could be iterated from start until one URL works. Currently there is the additional download in index that doesn't use the backup url.

@sandor-trombitas sandor-trombitas marked this pull request as ready for review August 7, 2024 08:03
@sandor-trombitas sandor-trombitas requested a review from a team as a code owner August 7, 2024 08:03
@j-luong j-luong force-pushed the CLI-415-binary-url branch from 1a3d0d1 to 4c956e5 Compare August 16, 2024 08:25
@sandor-trombitas sandor-trombitas force-pushed the CLI-415-binary-url branch 2 times, most recently from 9ab07fe to cead704 Compare August 16, 2024 11:23
feat: add utm source search param when downloading the binary

fix: prepare environment script

chore: fix lint issues

test: add test case for downloadWithBackup()

feat: add integration env vars

refactor: consolidate download locations to single method

chore: cleanup

chore: improve logging with timestamps

chore: format and lint
@sandor-trombitas sandor-trombitas merged commit 438337e into main Aug 16, 2024
11 checks passed
@sandor-trombitas sandor-trombitas deleted the CLI-415-binary-url branch August 16, 2024 13:04
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 this pull request may close these issues.

3 participants