SSWConsulting / SSWConsulting/SSW.Rules
CI/CD – Using Azure Key Vault for environment variables
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 26
- Forks
- 17
- Avg merge
- 14h 39m
- Merged PRs (30d)
- 2
Description
cc: @william-liebenberg @adamcogan
To Myself,
Currently the environment variables for Rules are undocumented and scattered all over the place.
- Create staging and production Azure Key Vaults
- Add a task to the build.yml pipeline that pulls the variables from Azure Key Vault. Each pipeline should pass through the connection string for the correct Azure Key Vault.
- Remove the variables from the Azure Pipelines
Thanks,
-Brady
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 build.yml and the existing Azure Pipelines configuration to find the current environment variables and pipeline connection settings. Check the Azure Key Vault task requirements for staging and production. Done means both vaults exist, each pipeline retrieves variables from the correct vault, and the variables are removed from Azure Pipelines.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100