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

Microsoft.KeyVault - secrets & keys missing from readme.azureresourceschema.md #11963

Closed
anthony-c-martin opened this issue Dec 4, 2020 · 3 comments · Fixed by #11964
Closed

Microsoft.KeyVault - secrets & keys missing from readme.azureresourceschema.md #11963

anthony-c-martin opened this issue Dec 4, 2020 · 3 comments · Fixed by #11964
Labels
KeyVault Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@anthony-c-martin
Copy link
Member

The following file is used to generate ARM template schemas for Microsoft.KeyVault: https://github.com/Azure/azure-rest-api-specs/blob/master/specification/keyvault/resource-manager/readme.azureresourceschema.md

The service supports the following API versions for vaults/secrets:

  • 2015-06-01
  • 2016-10-01
  • 2018-02-14-preview
  • 2018-02-14
  • 2019-09-01

The service supports the following API version for vaults/keys:

  • 2019-09-01

This should unblock the following PR:
Azure/azure-resource-manager-schemas#999

This should also address the following issue:
Azure/bicep#1077

This is somewhat related to:
#11929
@ghost ghost added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Dec 4, 2020
@anthony-c-martin anthony-c-martin mentioned this issue Dec 7, 2020
Merged
25 tasks
@erich-wang erich-wang added the Service Attention Workflow: This issue is responsible by Azure service team. label Dec 8, 2020
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Dec 8, 2020
@erich-wang
Copy link
Member

@anthony-c-martin, are you from KV or ARM team? To which team I should assign this issue?

@erich-wang erich-wang self-assigned this Dec 8, 2020
@anthony-c-martin
Copy link
Member Author

I'm on the ARM team. This issue should be assigned to the KV team.

@ghost
Copy link

ghost commented Dec 14, 2020

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @RandalliLama, @schaabs, @jlichwa.

Issue Details

The following file is used to generate ARM template schemas for Microsoft.KeyVault: https://github.com/Azure/azure-rest-api-specs/blob/master/specification/keyvault/resource-manager/readme.azureresourceschema.md

The service supports the following API versions for vaults/secrets:

  • 2015-06-01
  • 2016-10-01
  • 2018-02-14-preview
  • 2018-02-14
  • 2019-09-01

The service supports the following API version for vaults/keys:

  • 2019-09-01

This should unblock the following PR:
Azure/azure-resource-manager-schemas#999

This should also address the following issue:
Azure/bicep#1077

This is somewhat related to:
#11929

Author: anthony-c-martin
Assignees: erich-wang
Labels:

KeyVault, Service Attention
Milestone: -

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
KeyVault Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Milestone
No milestone
2 participants
@erich-wang @anthony-c-martin