[KeyVault] Update secrets tsp-location.yaml to new spec path for PFX-to-PEM (2025-07-01)#48445
Open
rohitsinghal4u wants to merge 3 commits intomainfrom
Open
[KeyVault] Update secrets tsp-location.yaml to new spec path for PFX-to-PEM (2025-07-01)#48445rohitsinghal4u wants to merge 3 commits intomainfrom
rohitsinghal4u wants to merge 3 commits intomainfrom
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the TypeSpec source location metadata for the Key Vault Secrets SDK package to align with a new Azure REST API Specs directory layout and commit reference.
Changes:
- Updated
directoryto point tospecification/keyvault/data-plane/Secrets. - Updated the pinned
commithash forAzure/azure-rest-api-specs. - Updated
additionalDirectoriesto include the newSecrets/commonpath.
You can also share your feedback on Copilot code review. Take the survey.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
…sVersion, SecretContentType - Add service versions V2025_06_01_PREVIEW and V2025_07_01; update getLatest() to V2025_07_01 - Add ContentType (impl) and public SecretContentType enum for PFX/PEM conversion - Add outContentType query parameter to getSecret/getSecretVersion public API - Add previousVersion field to SecretBundle and DeletedSecretBundle - Remove stale Accept header from purgeDeletedSecret interface and impl - Update tsp-location.yaml: new spec path, latest commit SHA, remove cleanup flag - Update CHANGELOG.md with 2025-07-01 GA release notes and feature descriptions - Update tests, samples, and customizations for new API capabilities
Contributor
API Change CheckAPIView identified API level changes in this PR and created the following API reviews |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Updates
tsp-location.yamlforazure-security-keyvault-secretsto point to the new unified TypeSpec spec path following the Key Vault folder structure refactor (azure-rest-api-specs#38668).Changes
directoryfromspecification/keyvault/Security.KeyVault.Secrets→specification/keyvault/data-plane/SecretscommitSHA to currentmainHEAD (30f8354c4b10115a7d48806e8a8e8d01277c513f) which includes theoutContentTypequery parameter added to thegetSecretoperation (azure-rest-api-specs#35604)additionalDirectoriesfromspecification/keyvault/Security.KeyVault.Common/→specification/keyvault/data-plane/Secrets/commonWhy
The old TypeSpec path
specification/keyvault/Security.KeyVault.Secretsno longer exists onmainofazure-rest-api-specs. All Key Vault TypeSpec sources were consolidated underspecification/keyvault/data-plane/in the repo refactor. Without this fix, the SDK generation pipeline cannot locate the TypeSpec sources and will fail.Related
outContentTypequery parameter togetSecretto support on-demand PFX→PEM certificate format conversion in API version2025-07-01Checklist
tsp-location.yamlis a code generation config file only; no public API changes in this PR