Skip to content

fix custom script handling for node/python/ruby/dotnet entry points #56

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.

Sign up for GitHub

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

Jump to bottom
Open
scott-es opened this issue May 23, 2022 · 1 comment
Open

fix custom script handling for node/python/ruby/dotnet entry points #56

scott-es opened this issue May 23, 2022 · 1 comment

Comments

@scott-es
Copy link
Contributor

scott-es commented May 23, 2022 •
edited
Loading

Expected behaviour

when using .snyk.d/prep.sh for node/python/ruby/dotnet, run_snyk is executed so that any custom commands are done before the rest of the script is executed.

Actual behaviour

when using .snyk.d/prep.sh for node, run_snyk is not executed. In the the language entrypoints, the custom script will run but run_snyk is also still called.
@scott-es
Copy link
Contributor Author

scott-es commented May 23, 2022 •
edited
Loading

target dates to resolve this:
node 6/6/22 #57
python 6/9/22
ruby 6/13/22
dotnet 6/20/22

@scott-es scott-es changed the title fix custom script handling for node.sh entrypoint fix custom script handling for node/python/ruby/dotnet entry points May 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@scott-es