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

Add python cli docker images #163

Closed
wants to merge 639 commits into from
Closed

Add python cli docker images #163

wants to merge 639 commits into from

Conversation

julienduchesne
Copy link
Contributor

@julienduchesne julienduchesne commented Jun 20, 2018

  • Ready for review
  • Follows CONTRIBUTING rules
  • Reviewed by Snyk internal team

What does this PR do?

Adds docker images which install the requirements.txt file located in the current directory into a virtualenv and runs the cli commands on that virtualenv.
docker run -it -e "SNYK_TOKEN={token}" -e "MONITOR=true" -v "$PWD:/project" snyk/snyk-cli:python3 test --project-name={project_name} --org={org_id}

joshje and others added 30 commits January 4, 2017 22:09
fix: add maven package format version
fix: sanitise maven exec params
* fix: adding the 'from' array to dependencies in maven

* fix: ensure root module is in 'from' array for multi-module dependencies
Many tools treat directories named 'test' as test directories and give them special treatment. Our lib/test directory is not a test directory - it holds code for 'snyk test'.

'yarn clean' is a prime example as it removes all directories named 'test' from a project's node_modules.

See: yarnpkg/yarn#2331
See: https://github.com/Snyk/snyk/issues/64
Ensures that we execute commands inside a shell and not directly.
This makes it easier to run commands on windows without nasty hacks
(like conditionally appending '.cmd' to the command string.. which
doesn't always work).

We originally used child_process.exec which actually calls
child_process.spawn under the hood with the shell option set to true.

Later we switched to using child_process.spawn directly without
realising that the shell option for spawn defaults to false and
has to be manually set.

Check out the docs:
https://nodejs.org/dist/latest-v6.x/docs/api/child_process.html#child_process_child_process_spawn_command_args_options
Now that we require authentication for running `snyk test`, we don't
want to introduce this command to the test suite by default, as all
environments will need to run `snyk auth` in order to authenticate.

This also introduces extra explanation that snyk test requires auth.
Explain that some commands require authentication, and give guidance
about how to authenticate.
We use a local MAC address to randomise sha1 to sign the message. In case MAC address is unreadable (CI env, for example), we defaulted to a random number, causing a crash in crypto.

Using `Math.random` is probably as random as `uuid`, but `crypto.createHash('sha1').update(mac)` requires a Buffer or a String, and not a number.
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.