-
Notifications
You must be signed in to change notification settings - Fork 148
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
base: main
Are you sure you want to change the base?
Changes from 10 commits
e0753da
e33f235
c9af674
9f1ef68
1fefc9f
8af920d
8c24844
357891f
f6ed85a
dcb0b8f
135be76
4a1b8b8
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Can the Storage Account rules in this script be handles the same way? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes certainly - planning to have a look at storage accounts after this. |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1 @@ | ||
__version__ = "0.11.17" | ||
__version__ = "0.11.18" |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,66 @@ | ||
#!/bin/bash | ||
|
||
function main() { | ||
|
||
set -o errexit | ||
set -o pipefail | ||
|
||
# parse params/set up inputs | ||
# | ||
if [[ -z "$TRE_ID" ]]; then | ||
echo -e "Could not add keyvault deployment network exception: TRE_ID is not set\nExiting...\n" | ||
exit 1 | ||
fi | ||
|
||
local RG_NAME="rg-${TRE_ID}" | ||
local KV_NAME="kv-${TRE_ID}" | ||
local MY_IP="${PUBLIC_DEPLOYMENT_IP_ADDRESS:-}" | ||
|
||
if [[ -z "$MY_IP" ]]; then | ||
MY_IP=$(curl -s "ipecho.net/plain"; echo) | ||
fi | ||
|
||
|
||
# add keyvault network exception | ||
# | ||
echo -e "\nAdding deployment network exception to key vault $KV_NAME..." | ||
|
||
if [[ -z "$(az group list --query "[?name=='$RG_NAME']" --output tsv)" ]]; then | ||
echo -e " Core resource group $RG_NAME not found\n" | ||
return 0 | ||
fi | ||
|
||
if [[ -z "$(az keyvault list --resource-group "$RG_NAME" --query "[?name=='$KV_NAME'].id" --output tsv)" ]]; then | ||
echo -e " Core key vault $KV_NAME not found\n" | ||
return 0 | ||
fi | ||
|
||
az keyvault network-rule add --resource-group "$RG_NAME" --name "$KV_NAME" --ip-address "$MY_IP" --output none | ||
|
||
local ATTEMPT=1 | ||
local MAX_ATTEMPTS=10 | ||
|
||
while true; do | ||
|
||
if KV_OUTPUT=$(az keyvault secret list --vault-name "$KV_NAME" --query '[].name' --output tsv 2>&1); then | ||
echo -e " Keyvault $KV_NAME is now accessible\n" | ||
break | ||
fi | ||
|
||
if [ $ATTEMPT -eq $MAX_ATTEMPTS ]; then | ||
echo -e "Could not add deployment network exception for $KV_NAME" | ||
echo -e "Unable to access keyvault $KV_NAME after $ATTEMPT/$MAX_ATTEMPTS.\n" | ||
echo -e "$KV_OUTPUT\n" | ||
|
||
exit 1 | ||
fi | ||
|
||
echo " Unable to access keyvault $KV_NAME after $ATTEMPT/$MAX_ATTEMPTS. Waiting for network rules to take effect." | ||
sleep 5 | ||
((ATTEMPT++)) | ||
|
||
done | ||
|
||
} | ||
|
||
main "$@" |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,43 @@ | ||
#!/bin/bash | ||
|
||
function main() { | ||
|
||
set -o errexit | ||
set -o pipefail | ||
|
||
# parse params/set up inputs | ||
# | ||
if [[ -z "$TRE_ID" ]]; then | ||
echo -e "Could not remove keyvault deployment network exception: TRE_ID is not set\nExiting...\n" | ||
exit 1 | ||
fi | ||
|
||
local RG_NAME="rg-${TRE_ID}" | ||
local KV_NAME="kv-${TRE_ID}" | ||
local MY_IP="${PUBLIC_DEPLOYMENT_IP_ADDRESS:-}" | ||
|
||
if [[ -z "$MY_IP" ]]; then | ||
MY_IP=$(curl -s "ipecho.net/plain"; echo) | ||
fi | ||
|
||
|
||
# remove keyvault network exception | ||
# | ||
echo -e "\nRemoving deployment network exception to key vault $KV_NAME..." | ||
|
||
if [[ -z "$(az group list --query "[?name=='$RG_NAME']" --output tsv)" ]]; then | ||
echo -e " Core resource group $RG_NAME not found\n" | ||
return 0 | ||
fi | ||
|
||
if [[ -z "$(az keyvault list --resource-group "$RG_NAME" --query "[?name=='$KV_NAME'].id" --output tsv)" ]]; then | ||
echo -e " Core key vault $KV_NAME not found\n" | ||
return 0 | ||
fi | ||
|
||
az keyvault network-rule remove --name "$KV_NAME" --ip-address "$MY_IP" --output none | ||
echo -e " Deployment network exception removed\n" | ||
|
||
} | ||
|
||
main "$@" |
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.
I don't have time to go over this the next few days and guess @marrobi is the same. Just wanted to point out we now have 2 vaults being used from the deployer point of view.
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.
When CMK is enabled another vault is created in the mgmt resource group