microsoft / microsoft/finops-toolkit
[PowerShell] Get-FinOpsHub (0.3)
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 get hub metadata in order to confirm the hub is setup correctly
💎 Solution
Update the Get-FinOpsHub command to include new settings and resources in 0.3.
⛔ Blocked
- Sync
features/exportsintodev, then intofeatures/powershell
Synopsis, syntax, description, and parameters should not change. We only need to update the output.
{
// ID is added as a cm-resource-parent tag to all deployed resources as part of the bicep code
id: "/subscriptions/.../resourceGroups/.../providers/Microsoft.Cloud/hubs/...",
// Type and name can be parsed out of the ID
type: "Microsoft.Cloud/hubs",
name: "...",
// Location would be pulled from the resources
location: "...",
properties: {
// Version, retention, and scopes pulled from settings.json
version: "0.3",
retention: {
ingestion: {
months: 13,
},
msexports: {
days: 0,
},
},
scopes: [{
scope: "...",
}],
// Resources determined at runtime via tags or saved in settings.json (TBD)
resources: {
dataFactory: "<data-factory-id>",
keyVault: "<keyvault-id>",
storage: "<storage-account-id>",
...
},
}
}
}
🙋♀️ Ask for the community
We could use your help:
- Please vote this issue up (👍) to prioritize it.
- Are there any parameters that are missing?
- 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 with the Get-FinOpsHub command, then inspect settings.json, the bicep code, and the required sync from features/exports through dev into features/powershell. Done means the command keeps its existing synopsis, syntax, description, and parameters while its output includes the specified hub metadata, settings, scopes, and runtime resources.
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
- Needs clarification
- Newbie friendliness
- 25/100