microsoft / microsoft/vscode-node-azure-pack
Feature Request: Add Azure Key Vault support
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 34
- Forks
- 40
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 2
Description
On my team, we lock down our key vaults by disabling public access and using private endpoints. But this means we cannot use the portal UI to manage secrets.
An Azure Tools extension with the ability to view, add, and edit secrets would be very helpful. Our engineer machines can access the Key Vault over private DNS using the private endpoint so a local tool like this would work great.
There are a couple third-party extensions but we do not trust them. A Microsoft-built VSCode extension for Key Vault management would solve this problem for us.
Contributor guide
No contributing guide indexed for this repository
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 reviewing the existing Azure Tools VS Code extension and its Azure service integrations. Determine the entry points needed for Azure Key Vault access through private endpoints, with completion defined as reliably viewing, adding, and editing secrets.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, vscode
- Domain
- cloud, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100