Add sharding_key_issue_url to cluster tables
What does this MR do and why?
This MR updates the database documentation YAML files for cluster-related tables to include sharding_key_issue_url. These URLs link to the issues created for defining sharding keys for these tables.
The following tables currently have desired_sharding_key defined but were missing the sharding_key_issue_url attribute, which is critical for tracking the progress of sharding implementation and providing context about the sharding decision:
cluster_providers_awscluster_providers_gcpclusters_kubernetes_namespaces
Please note that you should also add desired_sharding_key_migration_job_name in the same MR which you queue the backfill migration for the sharding key.
This is part of the ongoing database sharding effort and helps provide context and track the progress for making each table sharding-ready.
References
Related to:
- #553450 (closed) (cluster_providers_aws)
- #553451 (closed) (cluster_providers_gcp)
- #553454 (closed) (clusters_kubernetes_namespaces)
Related epic: &11670
Screenshots or screen recordings
This is a documentation-only change and does not affect the UI. No screenshots are required.
| Before | After |
|---|---|
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist.
It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.