Key Vault Admin and Readers
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- azure, yaml
- Domain
- authorization, cloud, infrastructure, security
Research direction
Start with iac-adb-360/pipelines/azure/configdev.yml and configprd.yml, then review how the pipeline uses these files to deploy the key vault. Verify the intended Resource Group, location, and Entra ID group object IDs for kvadmins and kvsecretreaders; done means both files contain the confirmed values and are updated on the dev branch.
Written by the indexing model from the issue text.
Description
2.1.3 edit the config yaml files found in /iac-adb-360/pipelines/azure/configdev.yml and configprd.yml to reflect the correct Resource Group name, location and the group object id's for the kvadmins as well as the kvsecretreaders. This groups are added as keyvault admins and keyvault secret readers in the key vault, which is going to be automatically deployed by the pipeline. So if not already done so, you'll have to create two groups p.ex. kvadmins and kvsecretreaders in Microsoft Entra ID, retrieve the OIDs and edit them in the two files accordingly. After you edit this files, they need to be updated in the repo. So if you were working locally, you'll have to commit and push to the repo.(make sure you are on the 'dev' branch)
I am not sure the purpose of this? Is it to assign the service principals the roles? If so wouldn't that be done directly against the service principal?
- Dominant language
- Python
- Stars
- 18
- Forks
- 56
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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/Databricks360
-
Commented out cellOpen
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
Azure/Databricks360#33 · 1 comment ·
-
Metastore CreationOpen
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
Azure/Databricks360#25 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 45/100
Azure/Databricks360#23 · 1 comment ·
All issues in Azure/Databricks360
Similar issues
-
docs pydanty:is-working
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
pydantic/pydantic-ai#8863 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
run-llama/llama_index#23278 ·
Maintainers usually reply within 2 days
-
documentation from-review-extraction github-actions priority: low severity:nit
Difficulty 1/5 Under an hour Newbie friendliness 92/100
LearningCircuit/local-deep-research#6946 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
oracle/langchain-oracle#323 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
tenstorrent/tt-metal#58057 · 1 comment ·
Maintainers usually reply within 1 day