Automated Key Vault provisioning and secrets management
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- azure, javascript
Research direction
Locate the template generator and read copilot-instructions.md for the existing Key Vault reference guidance. Trace how deployments, app settings, managed identities, and post-deployment documentation are generated, then use the acceptance criteria to verify provisioning, references, access, and rotation guidance.
Written by the indexing model from the issue text.
Description
Description
Deployed resources often require secrets (connection strings, API keys). Git-ape's copilot-instructions.md mentions Key Vault references (@Microsoft.KeyVault(...)) but there's no automated Key Vault provisioning or secrets wiring in the template generator.
Scope
- Auto-provision Key Vault — When a deployment includes resources that need secrets, auto-include a Key Vault in the template.
- Key Vault references — All app settings that contain secrets use
@Microsoft.KeyVault(...)references instead of inline values. - Secrets rotation guidance — Post-deployment runbook section on secrets rotation.
- Managed identity access — Auto-configure managed identity access policies on the Key Vault.
Acceptance Criteria
- Deployments with secret-consuming resources auto-include Key Vault.
- App settings use Key Vault references.
- Managed identity access to Key Vault is configured.
- Secrets rotation guidance included in post-deployment documentation.
- Dominant language
- JavaScript
- Stars
- 269
- Forks
- 48
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 14
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from Azure/git-ape
-
daily-status report
Difficulty 1/5 Under an hour Newbie friendliness 10/100
Maintainers usually reply within 1 day
-
agentic-workflows
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Maintainers usually reply within 1 day
-
report workshop-coverage
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
[workshop-update] docs(workshops): align Track 3 destroy lab with Deployment Stacks; glossary skillsOpenagentic-workflows workshop workshop-sync
Difficulty 2/5 1-3 hours Newbie friendliness 20/100
Azure/git-ape#378 · 1 comment ·
Maintainers usually reply within 1 day
-
agentic-workflows
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
Similar issues
-
Link Checker ReportOpenautomated issue report
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
0. to triage bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
sindresorhus/eslint-plugin-unicorn#3825 ·
Maintainers usually reply within 1 day