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.

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

Allow cert's custom policy for Import-AzKeyVaultCertificate cmdlet to be consistent with Azure CLI #20780

Closed
FabianGonzalez-MSFT opened this issue Jan 30, 2023 · 2 comments
Closed

Allow cert's custom policy for Import-AzKeyVaultCertificate cmdlet to be consistent with Azure CLI #20780

FabianGonzalez-MSFT opened this issue Jan 30, 2023 · 2 comments
Assignees
@BethanyZhou
Labels
feature-request This issue requires a new behavior in the product in order be resolved. KeyVault Tracking We will track status and follow internally

Comments

@FabianGonzalez-MSFT
Copy link

FabianGonzalez-MSFT commented Jan 30, 2023 •
edited
Loading

Description

Currently the "Import-AzKeyVaultCertificate" cmdlet does not allow a customer to import a certificate with a custom certificate's policy. The Key Vault API for Certificate Import allows the policy as part of the request's body and also, on Azure CLI you're allowed to import while inputting your own policy in JSON format: "az keyvault certificate import --policy @policy.json", however, that can't be done on PSH.

Issue script & Debug output

N/A

Environment data

N/A

Module versions

All

Error output

No response
@FabianGonzalez-MSFT FabianGonzalez-MSFT added bug This issue requires a change to an existing behavior in the product in order to be resolved. needs-triage This is a new issue that needs to be triaged to the appropriate team. labels Jan 30, 2023
@ghost ghost removed the needs-triage This is a new issue that needs to be triaged to the appropriate team. label Jan 30, 2023
@dingmeng-xue dingmeng-xue added KeyVault feature-request This issue requires a new behavior in the product in order be resolved. and removed bug This issue requires a change to an existing behavior in the product in order to be resolved. labels Feb 1, 2023
@isra-fel isra-fel added the Tracking We will track status and follow internally label Feb 2, 2023
@isra-fel
Copy link
Member

isra-fel commented Feb 2, 2023

Thanks @FabianGonzalez-MSFT for reporting.
We'll talk to keyvault team and cli team to discuss the feature and plan it.

@NoriZC NoriZC mentioned this issue Apr 7, 2023
Merged
1 task
@BethanyZhou
Copy link
Contributor

This feature will be available in next release, please expect it on 5/23.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@BethanyZhou BethanyZhou

Labels
feature-request This issue requires a new behavior in the product in order be resolved. KeyVault Tracking We will track status and follow internally
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@isra-fel @BethanyZhou @dingmeng-xue @FabianGonzalez-MSFT