-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[KeyVault] - Address a few items for keys and admin and bump service version #13759
Conversation
|
||
// For convenience in this sample we'll use some self-signed test certificates | ||
// that were generated using openssl | ||
const samplePfxBase64 = |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks suspicious but overall harmless - I just copied the same self signed test cert that dotnet uses instead of generating a different one https://github.com/Azure/azure-sdk-for-net/blob/311f34ea6ee203adb787b0319adf0415fbc30839/sdk/keyvault/Azure.Security.KeyVault.Certificates/tests/samples/Sample3_ImportCertificate.cs#L99-L204
Debated between inlining these and making PEM and PFX files - but those are gitignored so I figured it's not worth constantly having to force add them. Let me know if you think otherwise!
afbd357
to
f94b55e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome! Thank you 🌞
Update readme.python.md (Azure#13759)
What
curve
fromcreateECKeyOptions
tocreateKeyOptions
CertificatePolicy.contentType
is requiredWhy
createKeyOptions
is the catch-all and should accept parameters for all possible key creations (fixes [Key Vault Keys] createKey should accept "curve". #11263)Todo