[QUERY] Missing Resources After Updating Azure.ResourceManager.Hci to stable

[serg-sam]

Library name and version

Azure.ResourceManager.Hci 1.2.0

Query/Question

After upgrading the Azure.ResourceManager.Hci package from version 1.2.0-beta.1 to the stable 1.2.0, I noticed that several resources and related entities have been removed:

• VirtualMachineInstanceResource
• MarketplaceGalleryImageResource
• GalleryImageResource
• LogicalNetworkResource

These resources were originally added in the following commit:
7370480 (author: @pathuang-sia)

But later removed in this commit:
b2461f2 (author: @NikitaSingh-ms)

However, I can still see references to these resources in the latest stable API specification:
https://github.com/Azure/azure-rest-api-specs/tree/main/specification/azurestackhci/resource-manager/Microsoft.AzureStackHCI/stable/2024-01-01

Also, at least one of the removed resources is still referenced in the docs:
https://github.com/Azure/azure-docs-sdk-dotnet/blob/main/xml/Azure.ResourceManager.Hci/VirtualMachineInstanceResource.xml

Could you please clarify:

• Were these resources intentionally removed? If so, what was the reason?
• Should we expect them to return in upcoming patches or future releases?
• Will these resources be replaced with other types? (Or has it already been done?)

Environment

No response

[jsquire]

Thank you for your feedback. Tagging and routing to the team member best able to assist.

[pathuang-sia]

Hi @serg-sam,

The removal of these resources was due to two different teams sharing the same package for the Microsoft.AzureStackHCI resource provider. @NikitaSingh-ms generated the new package based off of their new stable version 2024-04-01. You can see that in the API folder we've separated into a folder structure to allow for different api release cadence: https://github.com/Azure/azure-rest-api-specs-pr/tree/RPSaaSMaster/specification/azurestackhci/resource-manager/Microsoft.AzureStackHCI/StackHCI/stable/2024-04-01

We originally wanted to release under a different package name but was advised to share the same package name by the dotnet team, so we should expect these deleted resources to return in future releases.

The resources won't be replaced with other types, but there may be new resources added.