Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

[Cosmos] Remove ephemeral-tenant provisioning from fixed-account live-test lanes

オープン
  • 何か問題がありますか？
#48,780 コメント 0 件 リアクション 1 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
45/100
issue の種類
リファクタリング
明瞭さ
おおむね明確
活発さ
活発
技術スタック
azure, powershell, python
領域
cloud, databases, devops

調査の方向性

PR #48459 と共有の live-test stage から始め、次に build-test-resource-config.yml、deploy-test-resources.yml、remove-test-resources.yml、test-resources.bicep を追跡します。fixed-account パスと AAD パスを分離し、fixed jobs では ephemeral provisioning を行わずに resolver と shared JSON secret を使用し、AAD では tenant-scoped role assignment を維持します。完了条件には、scoped stale-database cleanup、ownership documentation、重複する実行と利用できない deployment credentials の検証が含まれます。

索引モデルが issue の本文から書いたものです。

説明

Client Cosmos

Is your feature request related to a problem? Please describe.

PR #48459 moves the Python Cosmos key-auth live tests onto fixed, team-owned accounts and proves that the selected accounts work across the live matrix. However, the shared Python live-test stage still deploys and removes a temporary Cosmos account for every matrix leg before the fixed credentials are reapplied.

As a result, the migrated key-auth tests still authenticate through the ephemeral live-test tenant during ARM deployment. A tenant rotation or broken service connection can therefore fail the job before pytest reaches the fixed account. This is the final gap between the current Python implementation and Java's no-provisioning fixed-account model.

Describe the solution you'd like

Separate the live matrix by resource-lifecycle requirements and make the fixed-account lane independent of ephemeral-tenant provisioning.

  • Split the 12 fixed key-auth jobs and the already-fixed GSI job from the 7 AAD jobs that require a tenant-scoped Cosmos data-plane role assignment.
  • Run the fixed-account jobs through a Cosmos-owned stage or job that resolves credentials from the shared versioned JSON secret but does not invoke build-test-resource-config.yml, deploy-test-resources.yml, or remove-test-resources.yml.
  • Ensure the fixed-account jobs do not require the azure-sdk-tests-cosmos service connection or any authentication against the ephemeral tenant.
  • Keep the AAD jobs on the existing provisioned-resource path so test-resources.bicep can create their tenant-specific sqlRoleAssignment.
  • Move values currently supplied only as Bicep outputs into the fixed-account matrix. In particular, set AZURE_COSMOS_ENABLE_CIRCUIT_BREAKER=True on the applicable circuit-breaker jobs.
  • Remove the transitional post-deployment credential reapplication once fixed-account jobs no longer deploy resources; the resolver pre-step should become their sole source of ACCOUNT_HOST and ACCOUNT_KEY.
  • Add best-effort cleanup for databases left by cancelled or aborted runs. Cleanup must be limited to stale PythonSDKTest-* databases owned by Python and must run across each fixed account without affecting Java or concurrent Python runs.
  • Document ownership for Java's shared account provisioning/reconciliation script and the shared JSON secret update procedure, including a smoke test after account or key rotation.
  • Validate overlapping fixed-account runs and prove they remain runnable when ephemeral-tenant deployment credentials are unavailable.

Describe alternatives you've considered

  1. Keep the current transitional deployment followed by credential override. This is already proven by PR #48459, but it does not remove the tenant dependency.
  2. Move AAD tests onto the fixed accounts and refresh their role assignments after every tenant rotation. This preserves one matrix but requires cross-subscription permissions and additional identity lifecycle work.
  3. Add a per-leg deployment condition to shared eng templates. This is generic, but changes monorepo-wide infrastructure for a Cosmos-specific requirement.
  4. Register a separate AAD pipeline while keeping the fixed-account pipeline Cosmos-owned. This is fully service-local but adds another Azure DevOps pipeline definition to maintain.

Additional context

PR #48459 already supplies the prerequisites for this work:

  • A cross-platform PowerShell resolver compatible with Java's shared JSON-secret schema.
  • Stable-account selectors for all 12 key-auth matrix jobs; GSI already uses dedicated fixed credentials.
  • Run-scoped PythonSDKTest-* database naming, bounded control-plane retries, scoped normal cleanup, and test isolation needed for concurrent use.
  • Early resolver validation through PreSteps and a Cosmos-local post-deployment hook used during the transitional rollout.
  • Successful live verification of the fixed-account query, split, multi-region, and circuit-breaker coverage.

Related tracking issue: #48236. Java reference: Azure/azure-sdk-for-java#49735.

主要言語
Python
スター
5.6k
フォーク
3.4k
平均マージ
2日 4時間
マージ済み PR（30日）
200

環境構築

Codespaces で開く

このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

Azure/azure-sdk-for-python のほかの issue

Azure/azure-sdk-for-python の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。