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 support for strict-ssl config #1025

Merged
merged 6 commits into from
Oct 15, 2016

Conversation

TAGraves
Copy link
Contributor

This adds support for setting strict-ssl to false in npm config or in .yarnrc. The reason behind adding this support is to enable users of private registries with self-signed TLS certificates to use yarn.

I believe this is all that is needed to enable such support, but let me know if I have overlooked something. Also, let me know if some tests should be written for this feature.

This is dependent on #1024, as strict-ssl is a boolean option and it is impossible to set to false without 1024's fix.

@Daniel15
Copy link
Member

Hi @TAGraves! It looks like this diff fails lint due to some Flow errors: https://travis-ci.org/yarnpkg/yarn/jobs/167763999. Could you please fix those? Thank you! 😄

@TAGraves
Copy link
Contributor Author

@Daniel15 Sorry about that! I've fixed the errors, thanks!

// value if it exists
if (!val || val === DEFAULTS[key]) {
val = this.registries.npm.getOption(key) || val;
// if this isn't set in a yarn config, then use npm
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you please remove this commit from the PR, happy to accept the other option but I have problems with this code that I'll address in your other PR.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nevermind, this seems fine. Thanks!

@sebmck sebmck merged commit b0611a6 into yarnpkg:master Oct 15, 2016
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.

3 participants