fix: allow tests to be run against any snyk API #951
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lili2311
approved these changes
Jan 8, 2020
|
🎉 This PR is included in version 1.277.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
ghost
requested review from
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Allow CLI tests to be run against any snyk API.
Enables us to switch AppVeyor to test against our dev API.
How should this be manually tested?
SNYK_API="......" SNYK_API_KEY="......" npm testAny background context you want to provide?
Will clean up dashboards reporting CLI usage, at the moment AppVeyor clutters these dashboard with each CI run.