[AutoPR azure-resourcemanager-containerservice-preparedimgspec]-generated-from-SDK Generation - Java-6504708

[azure-sdk-automation]

Configurations: 'specification/containerservice/resource-manager/Microsoft.ContainerService/preparedimagespecification/tspconfig.yaml', API Version: 2026-02-02-preview, SDK Release Type: beta, and CommitSHA: 'e2d0f960c00562e907312009ba99aac82265d618' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6504708 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release.

[Copilot]

Copilot can't review bot-authored pull requests automatically. A user with Copilot access can request a review manually.

[weidongxu-microsoft]

namespace review not completed Azure/azure-sdk#10095

[weidongxu-microsoft]

service-dir in your tspconfig for java should be containerservice

[weidongxu-microsoft]

Running a new codegen with HEAD of Azure/azure-rest-api-specs#44338 into this branch, will re-open after that. (I had to revert the whole thing because of the wrong service dir)

tsp-location points on PR, not main

[weidongxu-microsoft]

OK. CI green.

We will need to wait for the completion of the namespace review PR, and do one more regen from specs main branch (after your specs PR merge).

If the namespace changes again, we will need to do one more reset on this branch (or maybe just use a new PR).

[aboodasfari]

Makes sense- does that mean I'm just waiting for namespace approval on Azure/azure-sdk#10095 at the moment?

Or do I need to get the specs PR merged before the issue linked above?

[weidongxu-microsoft]

You probably first wait for namespace approved. Then update the specs PR with the approved namespace / package name (before approval they are not final). Then merge and we can regen here.