Now that the local/pipelined position-budgets source is live in production, the PositionBudgets__Source feature flag and the legacy code path it guards can be retired.
Background
The flag was added to switch the personnel/position-budgets data source between the legacy Oracle path and the new local table:
- Config:
DatamartOptions.PositionBudgetsSource (env var PositionBudgets__Source), values UCPathDWH (default) vs Local.
- Dev defaulted to
Local; Prod opted in via an Azure App Setting.
- Local path:
usp_GetPositionBudgetsLocal (reads dbo.PositionBudgets).
- Legacy path:
usp_GetPositionBudgets (Oracle / OPENQUERY).
Prod is now on the local source, so the toggle is no longer needed.
Cleanup checklist
Notes
- Confirm prod has been stable on the local source before removing the fallback.
Now that the local/pipelined position-budgets source is live in production, the
PositionBudgets__Sourcefeature flag and the legacy code path it guards can be retired.Background
The flag was added to switch the personnel/position-budgets data source between the legacy Oracle path and the new local table:
DatamartOptions.PositionBudgetsSource(env varPositionBudgets__Source), valuesUCPathDWH(default) vsLocal.Local; Prod opted in via an Azure App Setting.usp_GetPositionBudgetsLocal(readsdbo.PositionBudgets).usp_GetPositionBudgets(Oracle / OPENQUERY).Prod is now on the local source, so the toggle is no longer needed.
Cleanup checklist
PositionBudgetsSourceoption fromDatamartOptionsand anyIOptionswiring / branching that selects the source.UCPathDWHbranch).PositionBudgets__Sourceapp setting from Azure (Dev/Test/Prod) once the code no longer reads it.usp_GetPositionBudgets(Oracle/OPENQUERY) sprocNotes