[AutoPR azure-security-keyvault-certificates]-generated-from-SDK Generation - Java-6316473#49210
Draft
azure-sdk wants to merge 3 commits into
Draft
[AutoPR azure-security-keyvault-certificates]-generated-from-SDK Generation - Java-6316473#49210azure-sdk wants to merge 3 commits into
azure-sdk wants to merge 3 commits into
Conversation
…nfig.yaml', API Version: 2026-03-01-preview, SDK Release Type: beta, and CommitSHA: 'ea20c467080ed3d3875c8b5aeff28ce52f6a55ca' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6316473 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release.
- Add public models.PlatformManaged wrapper with certificateUsage and metadata - Expose getPlatformManaged/setPlatformManaged on models.CertificatePolicy - Add CertificateServiceVersion.V2026_03_01_PREVIEW and make it the latest - Update CertificatesCustomizations to emit the new service version constant - Add PlatformManagedTest and CertificatePolicyTest unit tests - Add createCertificateWithPlatformManagedPolicy / updateCertificateWithPlatformManagedPolicy live tests on sync and async clients plus shared assertPlatformManagedPolicy helper - Update CHANGELOG.md to describe the new PlatformManaged feature Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…ayback tests - Revert CertificateServiceVersion.getLatest() back to V2025_07_01 so the existing test recordings (which are keyed by api-version) keep passing in playback. - Mirror the revert in CertificatesCustomizations so a future regeneration produces the same getLatest() body. - Mark the new createCertificateWithPlatformManagedPolicy / updateCertificateWithPlatformManagedPolicy parameterized tests with allowZeroInvocations = true so they are skipped (not errored) in environments where V2026_03_01_PREVIEW is not selected by AZURE_KEYVAULT_TEST_CERTIFICATE_SERVICE_VERSIONS. - Clarify CHANGELOG that V2026_03_01_PREVIEW is opt-in via serviceVersion(...). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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
2 participants
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.
Configurations: 'specification/keyvault/data-plane/Certificates/tspconfig.yaml', API Version: 2026-03-01-preview, SDK Release Type: beta, and CommitSHA: 'ea20c467080ed3d3875c8b5aeff28ce52f6a55ca' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6316473 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release.