[AutoPR Azure.ResourceManager.VirtualEnclaves]-generated-from-SDK Generation - .NET-5464929

[azure-sdk]

Configurations: 'specification/mission/Mission.Management/tspconfig.yaml', API Version: 2025-05-01-preview, SDK Release Type: beta, and CommitSHA: '1bd335533d57d11a33d41be9b5841e6986ec3567' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=5464929 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release. Release plan link: https://web.powerapps.com/apps/821ab569-ae60-420d-8264-d7b5d5ef734c?release-plan-id=2a4c3841-a7aa-f011-bbd3-6045bd08111b Submitted by: trevor.goodyear@microsoft.com

Release Plan Details

• Release Plan: https://aka.ms/sdk-release-planner?release-plan-id=2a4c3841-a7aa-f011-bbd3-6045bd08111b
  Spec pull request: Add Microsoft.Mission spec to public repo azure-rest-api-specs#32359
  Spec API version: 2025-05-01-preview

[Copilot]

Pull Request Overview

This PR updates the tsp-location.yaml for the VirtualEnclaves SDK to point to a new API spec commit for the 2025-05-01-preview release.

• Updates spec directory path to use forward slashes.
• Updates commit SHA to 1bd3355.
• Adds an empty additionalDirectories key.

[Copilot]

[nitpick] additionalDirectories is present but empty, which can be ambiguous. If no extra directories are required, remove the key; otherwise supply an explicit empty list (additionalDirectories: []) or the intended sequence of paths to avoid accidental null interpretation.

Suggested change

additionalDirectories:

[github-actions]

Hi @azure-sdk. Thank you for your interest in helping to improve the Azure SDK experience and for your contribution. We've noticed that there hasn't been recent engagement on this pull request. If this is still an active work stream, please let us know by pushing some changes or leaving a comment. Otherwise, we'll close this out in 7 days.

[github-actions]

Hi @azure-sdk. Thank you for your contribution. Since there hasn't been recent engagement, we're going to close this out. Feel free to respond with a comment containing /reopen if you'd like to continue working on these changes. Please be sure to use the command to reopen or remove the no-recent-activity label; otherwise, this is likely to be closed again with the next cleanup pass.