Skip to content

Unable to use custom repository #176

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
Closed
MichaelBellBOM opened this issue Apr 19, 2018 · 2 comments
Closed

Unable to use custom repository #176

MichaelBellBOM opened this issue Apr 19, 2018 · 2 comments

Comments

@MichaelBellBOM
Copy link

I am working on deploying a lambda function that uses custom libraries stored in Artifactory. Unfortunately when running sls deploy, the plugin fails because the --isolated argument causes the settings point towards our custom repository to be ignored and the jobs fails as it cannot find our custom library?

What is the reason for using the --isolated argument? And might it worth making it a parameter that could be overwritten?
@dschep dschep mentioned this issue Apr 19, 2018
Closed
@dschep
Copy link
Contributor

dschep commented Apr 19, 2018 •
edited
Loading

Hmm. It seems I added that based on an early suggestion (#8). But since then the pipCmdExtraArgs option has been added, so I think it makes sense to remove it so that custom repos, etc. can work.

@dschep dschep closed this as completed in 82b7420 Apr 19, 2018
@dschep
Copy link
Contributor

dschep commented Apr 19, 2018

Released as v4.0.1

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
2 participants
@dschep @MichaelBellBOM