Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Add support for syncing CCM resources (Cost Allocation Rules, Tag Pipelines)

Aperta
#698 0 commenti 1 reazione 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
52/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python
Ambito
api, cli

Direzione di ricerca

Start by comparing the existing dashboard, monitor, and logs-pipeline sync implementations and how they use the diff/dependency workflow. Review the Datadog endpoints /api/v2/cost/allocation/rules and /api/v2/tags/enrichment, then define support for the two listed resource types. Done means both resources can be replicated between organizations through the CLI.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Feature request

Currently datadog-sync-cli does not support syncing Cloud Cost Management (CCM) configuration resources across organizations. This includes:

  • Custom Allocation Rules (/api/v2/cost/allocation/rules or equivalent)
  • Tag Pipeline Rulesets (/api/v2/tags/enrichment)
  • Possibly other CCM artifacts (e.g. cost budgets, cost tag configurations)

Use case

As a Technical Account Manager managing multi-org enterprise customers (parent/child org structures), I regularly need to replicate CCM configuration — Allocation Rules and Tag Pipelines — from a source org to one or more destination orgs. Today this has to be done manually via the API, resource by resource, which does not scale well across many child orgs and is error-prone compared to the diff/sync workflow the tool already provides for other resource types (dashboards, monitors, logs pipelines, etc.).

Proposed resources

Resource API endpoint Notes
cost_allocation_rules GET/POST /api/v2/cost/allocation/rules Custom Allocation Rules
tag_pipeline_rulesets GET/POST /api/v2/tags/enrichment Tag Pipelines

Both are manageable via Terraform today (datadog_cloud_cost_management_* resources), so the underlying CRUD semantics should already be well defined.

Alternative considered

Doing this via direct API calls per organization — works but doesn't scale for TAMs managing many child orgs, and loses the diff/dependency-tracking benefits datadog-sync provides for other resource types.

Happy to provide more context or test against a real multi-org customer setup if useful.

Lingua principale
Python
Stelle
79
Fork
26
Merge medio
22h 1m
PR unite (30g)
25

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di DataDog/datadog-sync-cli

Tutte le issue di DataDog/datadog-sync-cli

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.