Skip to content

[AutoPR azure-mgmt-commvaultcontentstore]-generated-from-SDK Generation - Python-6481741#47641

Open
azure-sdk wants to merge 4 commits into
mainfrom
sdkauto/azure-mgmt-commvaultcontentstore-6476669
Open

[AutoPR azure-mgmt-commvaultcontentstore]-generated-from-SDK Generation - Python-6481741#47641
azure-sdk wants to merge 4 commits into
mainfrom
sdkauto/azure-mgmt-commvaultcontentstore-6476669

Conversation

@azure-sdk

@azure-sdk azure-sdk commented Jun 24, 2026

Copy link
Copy Markdown
Collaborator

Configurations: 'specification/liftrcommvault/Commvault.ContentStore.Management/tspconfig.yaml', SDK Release Type: beta, and CommitSHA: 'e7c377b4c801d6fe9e256ca22f6d6a79114026a7' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6481741 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release. Release plan link: https://azsdk-releaseplan-dashboard-hveph5aqhhcfhtgu.westus-01.azurewebsites.net/?releaseplan=2101 Submitted by: sauravraj@microsoft.com

Copilot AI review requested due to automatic review settings June 24, 2026 11:52

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds the brand-new management-plane SDK package azure-mgmt-commvaultcontentstore (initial beta 1.0.0b1), generated from TypeSpec (specification/liftrcommvault/Commvault.ContentStore.Management). It introduces the ContentStoreClient with operations for cloud accounts, storages, plans, protection groups, protected items, role mappings, and SaaS operations, along with the standard packaging, CI, samples, tests, and API metadata scaffolding.

Changes:

  • New azure-mgmt-commvaultcontentstore package scaffolding (pyproject, README, CHANGELOG, LICENSE, MANIFEST, version, py.typed, ci.yml, tsp-location).
  • Generated client/config/models/enums/operations surface (sync + aio) exposing ContentStoreClient.
  • Generated samples and skipped (@pytest.mark.skip) recorded tests plus conftest sanitizers and API metadata files.

Reviewed changes

Copilot reviewed 99 out of 101 changed files in this pull request and generated no comments.

Show a summary per file
File Description
sdk/commvaultcontentstore/ci.yml New CI pipeline definition with the package artifact entry.
.../tsp-location.yaml Pins TypeSpec source spec + commit for regeneration.
.../README.md Package readme; auth + client usage example matches the client API.
.../pyproject.toml Package metadata; correct beta stability flags and ContentStoreClient title.
.../CHANGELOG.md Initial 1.0.0b1 entry, date matches current date.
.../_version.py VERSION = "1.0.0b1", consistent with changelog.
.../_client.py, aio/_client.py ContentStoreClient with correct credential, subscription_id, base_url signature.
.../models/, operations/, _configuration.py, _enums.py, _validation.py, _utils/* Generated source (per mgmt rules, not reviewed in detail).
.../generated_samples/, generated_tests/, conftest.py Generated samples/tests (per mgmt rules, skipped).
.../MANIFEST.in, LICENSE, dev_requirements.txt, py.typed, apiview-properties.json, api.metadata.yml, _metadata.json Standard packaging/metadata scaffolding.

@ChenxiJiang333

Copy link
Copy Markdown
Member

/azp run prepare-pipelines

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines successfully started running 1 pipeline(s).

@azure-sdk azure-sdk changed the title [AutoPR azure-mgmt-commvaultcontentstore]-generated-from-SDK Generation - Python-6476669 [AutoPR azure-mgmt-commvaultcontentstore]-generated-from-SDK Generation - Python-6481741 Jun 25, 2026
@ChenxiJiang333

Copy link
Copy Markdown
Member

Client name: CommvaultContentStoreMgmtClient

@ChenxiJiang333

ChenxiJiang333 commented Jun 25, 2026

Copy link
Copy Markdown
Member

Hi @sauravraj62, the new api version 2026-07-03-preview seems not deployed on portal yet, we recommend making sure the api version to be deployed before releasing the SDK, though we won't block the release in self-serve release flow.

@ChenxiJiang333

ChenxiJiang333 commented Jun 25, 2026

Copy link
Copy Markdown
Member

Hi @sauravraj62, we have approved the PR and we will hold the PR merge and release until your explicitly ping us to merge then release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants