microsoft / microsoft/finops-toolkit
[Hubs] Backfill data after creating exports
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 603
- Forks
- 248
- Avg merge
- 7d 11h
- Merged PRs (30d)
- 11
Description
⚠️ Problem
When we create a new export, we don't populate it with data because we don't want to re-run every historical export. This means new exports that are created don't get populated until someone opens ADF, which is a non-obvious and confusing step for someone who doesn't have experience with ADF.
🛠️ Solution
After creating the export, check to see if a folder exists for that scope. If not, create a placeholder folder and run the backfill pipeline. If the folder does exist, then don't run the backfill pipeline.
🙋♀️ Ask for the community
We could use your help:
- Please vote this issue up (👍) to prioritize it.
- Leave comments to help us solidify the vision.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by locating the export-creation entry point and tracing how scope folders and the ADF backfill pipeline are handled. Done means newly created exports are populated when no folder exists, while existing folders do not trigger a backfill.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, data-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100