microsoft / microsoft/finops-toolkit
Modify toolkit to allow user to specify an existing Key Vault in a different Subscription
Open
Nobody has claimed this yet.
Tool: FinOps hubs
Type: Feature 💎
- Dominant language
- PowerShell
- Stars
- 603
- Forks
- 248
- Avg merge
- 7d 11h
- Merged PRs (30d)
- 11
Description
📝 Scenario
My company manage the deployment of all Key Vaults into a single platform subscription.
💎 Solution
Modify the toolkit to allow the user to specify an existing Key Vault (in a different Subscription) to be used.
🙋♀️ Ask for the community
- 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 toolkit entry point that provisions or references Key Vaults; no file or test is named in the issue. Trace how the vault is currently selected, then define how an existing vault in another subscription should be supplied and verify the deployment path against that scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100