Update KeyVault references#4112
Conversation
Unit Test Results0 tests 0 ✅ 0s ⏱️ Results for commit 5011793. ♻️ This comment has been updated with latest results. |
|
/test-extended |
|
🤖 pr-bot 🤖 🏃 Running extended tests: https://github.com/microsoft/AzureTRE/actions/runs/11498586135 (with refid (in response to this comment from @marrobi) |
|
What does it mean that it cascades the update? |
So that it updates the API app configuration values when the key vault secret version is updates. It seems that terraform doesn't always update the reference. As per issue discussion see - hashicorp/terraform-provider-azurerm#3129 (comment) |
|
/test-extended |
|
🤖 pr-bot 🤖 🏃 Running extended tests: https://github.com/microsoft/AzureTRE/actions/runs/11704066429 (with refid (in response to this comment from @yuvalyaron) |
|
/test-extended |
|
🤖 pr-bot 🤖 🏃 Running extended tests: https://github.com/microsoft/AzureTRE/actions/runs/11708350316 (with refid (in response to this comment from @marrobi) |
Fixes #4110 #2463
This pull request updates the references to KeyVault secrets in the code. The AAD_TENANT_ID, API_CLIENT_ID, and API_CLIENT_SECRET references are now constructed using the version so terraform cascades the update.