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

No documentation for DNS (SAN) in New-AzKeyVaultCertificatePolicy #11203

Closed
abatishchev opened this issue Feb 27, 2020 · 3 comments · Fixed by #12785
Closed

No documentation for DNS (SAN) in New-AzKeyVaultCertificatePolicy #11203

abatishchev opened this issue Feb 27, 2020 · 3 comments · Fixed by #12785
Assignees
Labels
Azure PS Team Doc - Reference feature-request This issue requires a new behavior in the product in order be resolved. KeyVault

Comments

@abatishchev
Copy link

abatishchev commented Feb 27, 2020

Description of the new feature

The documentation for New-AzKeyVaultCertificatePolicy has no examples nor details how to create a certificate with one or multiple SANs.

Also it doesn't explain that the DNS parameter actually means SAN. There are no results if you search for "SAN" or "alternative" on the page.

P.S.

Docs for PowerShell doesn't allow to open a GitHub issue like what for instance Service Fabric does.

@abatishchev abatishchev added Azure PS Team feature-request This issue requires a new behavior in the product in order be resolved. triage labels Feb 27, 2020
@abatishchev
Copy link
Author

@dingmeng-xue hi, do you know if there is a chance this to be addressed in a near future?

@dingmeng-xue
Copy link
Member

Since functions provided by service team, we need to talk with KeyVault team to understand the example.
Docs for Azure PowerShell are synced from azure-powershell repo. If there is any question to docs, feel free to raise issue to this repo.

@abatishchev
Copy link
Author

@dingmeng-xue, please ping the service team.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Azure PS Team Doc - Reference feature-request This issue requires a new behavior in the product in order be resolved. KeyVault
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants