microsoft / microsoft/finops-toolkit
[PowerShell] Deploy-FinOpsHub โ Local template file
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 603
- Forks
- 248
- Avg merge
- 7d 11h
- Merged PRs (30d)
- 11
Description
๐ Scenario
As a hub admin, I need to deploy a hub from a local template in order to deploy my customized template
๐ Solution
Update Deploy-FinOpsHub command to support deploying a local template.
Synopsis stays the same. Initialization will happen automatically, so there are no new parameters.
Syntax
Deploy-FinOpsHub `
... `
[-TemplateFile <string>]
Description
The Deploy-FinOpsHub command creates a new FinOps hub instance. If the -TemplateFile parameter is specified, that is the template that is used; otherwise, the FinOps hub template is downloaded from GitHub using the specified version.
FinOps hubs has certain prerequisites that must be met before the template can be deployed. The Deploy-FinOpsHub command will internally call Initialize-FinOpsHubDeployment to validate and apply these requirements. Initialization must be done by a subscription contributor due to resource provider registration. Resource group contributors can execute the Deploy-FinOpsHub command but it will fail if these requirements are not met. Note initialization does not account for any custom requirements when -TemplateFile is specified.
Parameters
| Parameter | Description |
|---|---|
| ... | |
-TemplateFile |
Optional. Path to the template file to deploy. |
๐โโ๏ธ 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
Start by locating the Deploy-FinOpsHub command and its existing template-download path, then inspect how it invokes Initialize-FinOpsHubDeployment. Implement support for the optional -TemplateFile path while preserving the GitHub download behavior when it is omitted, and verify both paths with the repository's existing tests or command validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100