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

Update crypto imports #5571

Merged
merged 5 commits into from
Oct 23, 2019
Merged

Update crypto imports #5571

merged 5 commits into from
Oct 23, 2019

Conversation

AnthonyMacKinnon
Copy link
Contributor

Referencing packages that import crypto in a Node project causes the following warnings on start:

[DEP0091] DeprecationWarning: crypto.DEFAULT_ENCODING is deprecated.
[DEP0010] DeprecationWarning: crypto.createCredentials is deprecated. Use tls.createSecureContext instead.
[DEP0011] DeprecationWarning: crypto.Credentials is deprecated. Use tls.SecureContext instead.

For more detail, see nodejs/node#23203.

@msftclas
Copy link

msftclas commented Oct 15, 2019

CLA assistant check
All CLA requirements met.

@AnthonyMacKinnon
Copy link
Contributor Author

Assuming this gets merged, do we need to make a separate PR for the @next (v12) version as well or is the plan to eventually merge changes from master?

@HarshaNalluru
Copy link
Member

Thank you so much for fixing this, @AnthonyMacKinnon.
We keep the v12(feature/storage branch) in sync with the master by frequently merging the master branch.
Looks like the changes in this PR cover all the instances of * as crypto in the feature/storage branch as well. Hence, no need to make a separate PR for v12.

@HarshaNalluru HarshaNalluru added the Client This issue points to a problem in the data-plane of the library. label Oct 18, 2019
@HarshaNalluru
Copy link
Member

Hey @AnthonyMacKinnon,

Can you please resolve the merge conflicts?
We would like to merge this soon. 😀

@AnthonyMacKinnon
Copy link
Contributor Author

@HarshaNalluru Absolutely, I wasn't sure if we needed to wait until everyone approved it. Merge done!

@HarshaNalluru
Copy link
Member

Thanks, @AnthonyMacKinnon!

@ramya-rao-a
Copy link
Contributor

/azp run js - storage - ci

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@ramya-rao-a
Copy link
Contributor

/azp run js - keyvault - ci

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@ramya-rao-a
Copy link
Contributor

/azp run js - appconfiguration - ci

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@ramya-rao-a ramya-rao-a merged commit 87b3ae3 into Azure:master Oct 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Client This issue points to a problem in the data-plane of the library.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants