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?
Up until now the analytics payload that we send did not include the organisation specified as the --org parameter.
While normal calls to
snyk test
resulted in the right org, analytics was saving data to the user's default organisation.This change now correctly collects the specified org so that the data is connected correctly.
How should this be manually tested?
Run a local backend and point your snyk CLI there.
Set a breakpoint in
analytics.js
line 8 (to capture the/cli
API call).Run
snyk test --org=<some org other than your preferred or default org>
Notice the organisation is now the one specified by
--org
!Any background context you want to provide?
Report in #boost-asks
What are the relevant tickets?
Jira ticket BST-425