▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ Bicep Cost Estimator ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ Estimate Azure costs directly from Bicep and ARM templates. ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ title : Roadmap ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ page : https://bicepcostestimator.net/roadmap ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ repo : https://github.com/polatengin/washington ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ The following features are planned for future releases: • 0 - Publish platform-specific binaries as GitHub releases for faster Action startup (no build step needed) • 0 - Publish purpose-built images for the docs site and the CLI so the website image stays focused on serving docs while the CLI image is smaller and optimized for local and CI command execution • 0 - Support Bicep projects that span multiple files and use modules • 0 - Let the browser playground load local modules and separate parameter files instead of requiring a single self-contained template • 0 - Allow users to upload Bicep, ARM, and parameter files in the browser playground and run cost estimation without pasting template contents manually • 0 - Run two templates or two parameter sets side by side in the browser and show total and per-resource cost deltas • 0 - Generate command, option, and help output docs directly from the CLI to prevent the docs from drifting from the implementation • 0 - Add end-to-end guides for common workflows like estimating a Bicep app, comparing dev vs prod, validating CI budgets, and debugging missing prices • 0 - Improve the docs search with filters, highlighted matches, and better ranking so users can find commands, guides, and resource support pages faster • 0 - Let users group the VS Code extension tree by service, resource type, file, or warning status, and click items to jump to the corresponding resource declaration • 0 - Keep the VS Code extension cost breakdown panel and status bar automatically in sync with LSP updates for the active file instead of relying mainly on manual commands • 1 - Add a VS Code command or UI to choose a matching  .bicepparam  file, switch between parameter sets, and apply temporary overrides from inside the editor • 0 - Offer VS Code quick fixes or suggestions when the estimate is incomplete, such as adding explicit locations, checking unsupported resource types, or opening related docs • 0 - Add a dedicated VS Code webview for charts, top cost drivers, grouped subtotals, warnings, and copy/export actions for the current estimate • 0 - Compare the current file against another params file, a saved baseline, or another branch/workspace file directly inside VS Code • 0 - Let users open supported-resources docs or Microsoft Learn pages from the VS Code tree view, hover, or CodeLens • 0 - Improve VS Code extension behavior in WSL, dev containers, and SSH remotes so CLI resolution and bundled binaries work predictably across environments • 0 - Increase automated test coverage across the CLI, VS Code extension, website, and GitHub Action to catch regressions earlier • 0 - Add more real-world Bicep, ARM, params, and module fixtures that cover additional Azure services, edge cases, and larger project layouts • 0 - Build more tests around shared fixtures so pricing logic, extraction behavior, and output formatting stay stable as support expands • 0 - Add broader end-to-end CLI tests for commands, output formats, warnings, parameter handling, and comparison workflows • 0 - Expand tests for LSP startup, commands, CodeLens, tree views, status bar updates, and editor workflows • 0 - Add automated tests for docs search, playground submissions, estimate rendering, upload flows, and browser-side error handling • 0 - Enforce minimum coverage and required test suites in CI before shipping changes to pricing, docs, playground, or extension features • 2 - Support a  .bce.json  or  .bce.yaml  file for shared defaults like region, output format, cache TTL, and estimation settings • 2 - Compare costs across different parameter sets (for example,  dev  vs  prod ) • 0 - Let users choose or define estimation profiles for things like storage growth, transaction volume, and baseline throughput • 0 - Compare the same deployment across Azure regions to highlight pricing deltas and default-region assumptions • 0 - Detect cost changes over time as Azure pricing evolves • 2 - Show cost delta vs current deployment ( bce estimate diff main.bicep ) • 1 - Add ANSI colors, styled tables, and clearer warning/success formatting in CLI output, with  --no-color  and plain-text fallbacks for CI and redirected output • 0 - Allow users to customize the GitHub Action PR comment format • 1 - Add a  --currency  flag to the CLI and GitHub Action for non-USD currencies • 0 - Show RI and savings plan pricing alongside pay-as-you-go for comparison • 0 - Integrate cost warnings into GitHub Code Scanning and the security tab • 0 - Recommend cheaper SKUs, redundant resources, or right-sizing opportunities • 0 - Add breakdowns by service, resource type, location, or module, and highlight the biggest cost drivers • 0 - Group and subtotal costs by Azure resource tags (team, project, environment) • 0 - Add service-level and type-level visual summaries above the raw estimate table • 0 - Export a self-contained report with charts, subtotals, and collapsible resource sections for sharing in PR artifacts • 0 - Let estimate result rows open official Microsoft Learn documentation for the corresponding Azure resource type • 0 - Show which file, module, or declaration produced each estimated resource so users can trace costs back to the source • 0 - Show spot and low-priority pricing alongside pay-as-you-go • 0 - Save an approved estimate and compare future runs against it, even when there is no live deployment to diff against • 0 - Support Enterprise Agreement and CSP pricing via user-provided rate cards • 0 - Show costs beyond monthly (quarterly, annual) • 0 - Resolve modules from Azure Container Registry and template specs