microsoft / microsoft/finops-toolkit
[Hubs][PowerShell] Start-FinOpsHubBackfill
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 603
- Forks
- 248
- Avg merge
- 7d 11h
- Merged PRs (30d)
- 11
Description
📝 Scenario
As a FinOps practitioner, I need to backfill data in order to view historical data in reports
💎 Solution
Create a Start-FinOpsHubBackfill command to run the config_RunBackfillJob pipeline.
Synopsis
Starts the backfill process for all FinOps hubs scopes.
Syntax
# Backfill everything
Start-FinOpsHubBackfill `
[-Name] <String> `
[-ResourceGroupName <String>]
# Backfill a date range
Start-FinOpsHubBackfill `
[-Name] <String> `
[-ResourceGroupName <String>] `
-StartDate <DateTime> `
[-EndDate <DateTime>]
Description
The Start-FinOpsHubBackfill command runs the backfill process to load or reload data for the specified period for all scopes.
Parameters
| Parameter | Description |
|---|---|
| '‑Name' | Optional. Name of the FinOps hub instance. Supports wildcards. |
| '‑ResourceGroupName' | Optional. Name of the resource group the FinOps hub was deployed to. Supports wildcards. |
-StartDate |
Optional. Day to start running exports. If not specified, will backfill all months based on the retention period. |
-EndDate |
Optional. Last day to run the export. If -StartDate is specified, will default to the end of the same month. |
ℹ️ Additional info
Get-AzDataFactoryV2 `
-ResourceGroupName "{hub-resource-group}" `
-ErrorAction SilentlyContinue `
| ForEach-Object {
Invoke-AzDataFactoryV2Pipeline `
-ResourceGroupName $_.ResourceGroupName `
-DataFactoryName $_.DataFactoryName `
-PipelineName 'config_RunBackfillJob'
}
🙋♀️ Ask for the community
We could use your help:
- Please vote this issue up (👍) to prioritize it.
- Do we need an option to only backfill one scope?
- Should the backfill process have an option to detect missing data and only backfill missing data?
- 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
Start by locating the existing PowerShell command patterns and the Azure Data Factory entry point named config_RunBackfillJob. Review how hub and resource-group filters and date parameters are handled, then confirm whether scope selection and missing-data detection remain open design questions before defining done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, powershell
- Domain
- cli, cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100