Board Review: Management Plane Namespace Review managedccfs

[prathod09]

Thank you for submitting this review request. Thorough review of your management library namespaces ensures that your library names are consistent with the guidelines and the consumers of your management library have a consistently good experience when using Azure.

To ensure consistency, all language library names will generally be reviewed together.

Before submitting, ensure you adjust the title of the issue appropriately.

Note that the required material must be included before a meeting can be scheduled.

Contacts and Timeline

• Responsible service team: Azure Confidential Computing Ledger
• Main contacts: pratikrathod@microsoft.com, settiy@microsoft.com
• Expected code complete date: 05/26/23
• Expected release date: 07/12/2023

About the Service (required)

• Link to documentation introducing/describing the service: https://microsoftservicetree.com/services/c0fb4fa3-73f4-415e-b2a1-ecdda435f71b
• Link to the service REST APIs Specs: https://github.com/Azure/azure-rest-api-specs/blob/main/specification/confidentialledger/resource-manager/Microsoft.ConfidentialLedger/preview/2023-01-26-preview/managedccf.json
• Link to GitHub issue for previous review sessions, if applicable: N/A

Namespace Proposals (required per language)

In the examples below please replace every occurrence of managedccfs with your the service resource provider name. Be sure to keep the casing shown with managedccfs when replacing it with the service resource provider name.

• .NET: Azure.ResourceManager.ManagedCcfs
• Java: azure-resourcemanager-managedccfs (com.azure.resourcemanager.managedccfs)
• Go/Golang: sdk/resourcemanager/managedccfs/arm-managedccfs
• JavaScript: @azure/arm-managedccfs
• Python: azure-mgmt-managedccfs

Thank you!

[ArthurMa1978]

There is no need for a separate namespace or SDK package because this is part of ConfidentialLedger.

[ronniegeraghty]

Closing as there is no need for new mgmt libraries.