- Project is Maven.
- Java code is on JDK 8 or above.
It is recommended to use azure-sdk-bom (version higher than 1.3.0).
The intention is to investigate whether including the TypeSpec authoring chatbot MCP in the Azure/azure-rest-api-specs repository can help GitHub Copilot better handle user issues and PR reviews.
One champion scenario I'd imagine would be:
Issue by user with description like below:
1. Add preview api-version 2025-09-01 to RP <resource-provider>
2. Add resource <resource> with path <route>, including standard CRUD operations on this resource
Follow up on https://gist.github.com/weidongxu-microsoft/fa420c35cf0611a62a8d155771dd3425
With @armRenameListByOperation solved, we can put multiple List operation into same Interface.
TypeSpec dev advises against this approach.
TCGC, by default, groups operations via TypeSpec Interfaces.
If @operationGroup is specified in client.tsp, it would group operations from Interfaces with @operationGroup in client.tsp instead.
Swagger in Management usually groups many different resources in a single resource group, via "operationId".
Related issue:
PR
DevBox resource model is
Information and runtime behavior of the new design can be found at cadl-ranch PR
Major difference in PUT.
Resource object, not the OperationStatus object.Resource URL preferred to be omitted. The Resource object from the PUT is already the final result.Major difference in POST.
| /** | |
| * Copyright (c) Microsoft Corporation. All rights reserved. | |
| * Licensed under the MIT License. See License.txt in the project root for | |
| * license information. | |
| */ | |
| package com.microsoft.azure.azuresdktest; | |
| import com.google.common.io.BaseEncoding; | |
| import com.microsoft.aad.adal4j.AsymmetricKeyCredential; |