-
Notifications
You must be signed in to change notification settings - Fork 158
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Core key vault firewall should not be set to "Allow public access from all networks" #4260
Core key vault firewall should not be set to "Allow public access from all networks" #4260
Conversation
…m all networks" #4250
Unit Test Results0 tests 0 ✅ 0s ⏱️ Results for commit f2c8c96. ♻️ This comment has been updated with latest results. |
/test 8af920d |
🤖 pr-bot 🤖 🏃 Running tests: https://github.com/microsoft/AzureTRE/actions/runs/12660338621 (with refid (in response to this comment from @jonnyry) |
/test-extended 8af920d |
🤖 pr-bot 🤖 🏃 Running extended tests: https://github.com/microsoft/AzureTRE/actions/runs/12661150197 (with refid (in response to this comment from @jonnyry) |
/test-destroy-env |
Destroying PR test environment (RG: rg-tre26f9d939)... (run: https://github.com/microsoft/AzureTRE/actions/runs/12669260987) |
/test 2970a5d |
🤖 pr-bot 🤖 🏃 Running tests: https://github.com/microsoft/AzureTRE/actions/runs/12669597448 (with refid (in response to this comment from @jonnyry) |
2970a5d
to
dcb0b8f
Compare
/test 272589f |
🤖 pr-bot 🤖 🏃 Running tests: https://github.com/microsoft/AzureTRE/actions/runs/12670289419 (with refid (in response to this comment from @jonnyry) |
/test bf9fd32 |
🤖 pr-bot 🤖 🏃 Running tests: https://github.com/microsoft/AzureTRE/actions/runs/12670349633 (with refid (in response to this comment from @jonnyry) |
/test-destroy-env |
Destroying PR test environment (RG: rg-tre26f9d939)... (run: https://github.com/microsoft/AzureTRE/actions/runs/12670413797) |
bf9fd32
to
dcb0b8f
Compare
PR test environment destroy complete (RG: rg-tre26f9d939) |
/test |
🤖 pr-bot 🤖 🏃 Running tests: https://github.com/microsoft/AzureTRE/actions/runs/13230152187 (with refid (in response to this comment from @jonnyry) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested locally, LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work!
/test-destroy-env |
Destroying PR test environment (RG: rg-tre26f9d939)... (run: https://github.com/microsoft/AzureTRE/actions/runs/13306311442) |
PR test environment destroy complete (RG: rg-tre26f9d939) |
/test f2c8c96 |
🤖 pr-bot 🤖 🏃 Running tests: https://github.com/microsoft/AzureTRE/actions/runs/13306353906 (with refid (in response to this comment from @jonnyry) |
@marrobi another unexpected "resource already exists error". Performed a Can just force approve this one if you are ok with that?
|
@jonnyry I think it takes a bit of time for the storage name to become available again, it can get cached at the Azure platform side for a while. If run again it will likely work. |
/test-force-approve Tested locally. |
🤖 pr-bot 🤖 ✅ Marking tests as complete (for commit f2c8c96) (in response to this comment from @marrobi) |
ah right, yes DNS issues |
Resolves #4250
What is being addressed
PUBLIC_DEPLOYMENT_IP_ADDRESS
variable if set) during deploymentHow is this addressed
A new script to add and remove the keyvault deployment IP exception:
devops/scripts/kv_add_network_exception.sh
They are called from the following scenarios in order to provider access to KV:
core/terraform/deploy.sh
core/terraform/scripts/letsencrypt.sh
devops/scripts/destroy_env_no_terraform.sh
core/terraform/destroy.sh
The script uses a bash trap so that it runs regardless of whether the preceeding code fails or not, to ensure the IP exception is removed
A bug in azurerm provider was encountered which required the use of a terraform provisioner:
azurerm_key_vault
was required to work around an azurerm provider bug which means if a key vault is being re-created (it was previously soft deleted), the network acls are not updated. This can be removed when the bug is fixed, or a different workaround found.Updates since inital commit (as discussed with @marrobi):
devops/scripts/key_vault_list.sh
devops/scripts/set_contributor_sp_secrets.sh