Skip to content

[Automation] Generate SDK based on TypeSpec 0.40.0 DEV#48179

Closed
azure-sdk wants to merge 1 commit intoAzure:mainfrom
azure-sdk:typespec-java-generation-5945154
Closed

[Automation] Generate SDK based on TypeSpec 0.40.0 DEV#48179
azure-sdk wants to merge 1 commit intoAzure:mainfrom
azure-sdk:typespec-java-generation-5945154

Conversation

@azure-sdk
Copy link
Collaborator

[Automation] Generate SDK based on TypeSpec 0.40.0 DEV

@azure-sdk azure-sdk added the DPG label Mar 2, 2026
@XiaofeiCao XiaofeiCao closed this Mar 2, 2026
github-merge-queue bot pushed a commit to microsoft/typespec that referenced this pull request Mar 6, 2026
- emitter part for
Azure/azure-sdk-for-java#47621
- autorest PR: Azure/autorest.java#3298
- sdk repo PR: Azure/azure-sdk-for-java#48226
- sync SDK PR looks good:
Azure/azure-sdk-for-java#48179

## Summary

Replace `AzureResourceManager` with SDK-specific `XXManager` as the
entry point in Fluent Premium samples.

Previously, premium samples were generated with `AzureResourceManager`
as the entry type and then moved to
`sdk/resourcemanager/azure-resourcemanager/samples` by the downstream
`generate.py` script. This change makes premium samples use the
corresponding `XXManager` (e.g., `ComputeManager`, `StorageManager`)
directly, so samples can stay in their own SDK location.

### Before vs After

```java
// Before: premium sample used AzureResourceManager
void sampleMethod(com.azure.resourcemanager.AzureResourceManager azure) {
    azure.storageAccounts().manager().serviceClient().getStorageAccounts().list();
}

// After: premium sample uses SDK-specific manager
void sampleMethod(com.azure.resourcemanager.storage.StorageManager manager) {
    manager.serviceClient().getStorageAccounts().list();
}
```

Will update `generate.py` when this got shipped.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants