Skip to content

Latest commit

 

History

History
125 lines (84 loc) · 9 KB

README.md

File metadata and controls

125 lines (84 loc) · 9 KB
Raw

Azure Conformance Tests Infrastructure

This folder contains helper scripts for maintainers to set up resources needed for conformance testing of Azure components.

If you are running on Windows, all automation described in this document will need to be executed under Git Bash

Prerequisites

To use the automation in this folder, you will need:

For running tests for Azure Event Grid, you also need to run a PowerShell script which requires:

Setting up Azure resources for conformance tests

The setup-azure-conf-test.sh script will create and configure all the Azure resources necessary for the Azure conformance tests. You will need to login the Azure CLI first, and set the target account you want to run the deployment under:

az login
az account set -s "Name of Test Deployment Subscription"
./setup-azure-conf-test.sh --user="[email protected]" --location="EastUS"

If you plan to run the bindings.azure.eventgrid test, you may also want to provide the --ngrok-token parameter at this point, or you will have to manually populate this value yourself in the test Key Vault or your local environment variable before your run the test.

For more details on the parameters that the script supports, run:

./setup-azure-conf-test.sh --help

By default, the script will prefix all resources it creates with your user alias, unless you provide it with an alternative --prefix string. It will generate several additional artifacts for your use after deployment to an output directory that defaults to $HOME/azure-conf-test unless otherwise specified by --outpath when running the script. Based on the example command for running the script, these would be:

  • myazurealias-azure-conf-test.json is a copy of the Azure Resource Manager (ARM) template compiled from the .bicep files in this folder, and used to generate all the resources. It can be modified and re-deployed if desired for your own purposes.
  • myazurealias-teardown-conf-test.sh is a script that will teardown all of the Azure resources that were created, including the test service principals and key vault.
  • myazurealias-conf-test-config.rc contains all the environment variables needed to run the Azure conformance tests locally. This file also contains various credentials used to access the resources.
  • AzureKeyVaultCert.pfx is a local copy of the cert for the Service Principal used in the secretstore.azure.keyvault conformance test. The path to this is referenced as part of the environment variables in the *-conf-test-config.rc.
  • AZURE_CREDENTIALS contains the credentials for the Service Principal you can use to run the conformance test GitHub workflow against the created Azure resources.

Setting up tests for Azure Event Grid

If you plan to run the bindings.azure.eventgrid tests, you will also need to run an additional PowerShell script to set up your Azure AD environment.

Make sure you have the environmental variables from myazurealias-conf-test-config.rc loaded in your environment before running this command. Otherwise, you can pass the

# Authenticate with the Microsoft Graph
# You may need to add the -TenantId flag to the next command if needed
Connect-MgGraph -Scopes "Application.Read.All","Application.ReadWrite.All"
./setup-eventgrid-sp.ps1 $env:AzureEventGridClientId

Note: if your directory does not have a Service Principal for the application "Microsoft.EventGrid", you may need to run the command Connect-MgGraph and sign in as an admin for the Azure AD tenant (this is related to permissions on the Azure AD directory, and not the Azure subscription). Otherwise, please ask your tenant's admin to sign in and run this PowerShell command: New-MgServicePrincipal -AppId "4962773b-9cdb-44cf-a8bf-237846a00ab7" (the UUID is a constant)

Deploying for use in GitHub workflows

If you are running the script to enable running the conformance test workflow in your fork of dapr/components-contrib, you will also need to run the allow-github-ips-in-azuresql.py script to allow the ports used by GitHub Actions through the test Azure SQL Server's firewall.

The script coalesces the IP addresses published by the GitHub meta API endpoint and adds them as firewall rules to the target SQL server, for example:

python3 allow-github-ips-in-azuresql.py --outpath ~/sql_firewall_settings --sqlserver "${AzureSqlServerName}" --resource-group "${AzureResourceGroupName}"

This script will also allow you to generate the template for adding the firewall rules without deploying them with the --no-deployment flag, so you can inspect the rules first as needed:

python3 allow-github-ips-in-azuresql.py --outpath ~/sql_firewall_settings --no-deployment

For more details on the parameters, run the script with the --help flag.

Running Azure conformance tests locally

  1. Apply all the environment variables needed to run the Azure conformance test from your device, by sourcing the generated *-conf-test-config.rc file. For example:

    source ~/azure-conf-test/myazurealias-conf-test-config.rc

  2. Follow the instructions for running individual conformance tests.

    The bindings.azure.eventgrid test and others may require additional setup before running the conformance test, such as setting up non-Azure resources like an Ngrok endpoint. See conformance.yml for details.

    The state.azure.sql test expects that the SQL Server firewall port has been opened to the test client. The GitHub workflow relies on all IPs used by GitHub Actions being allowed via the allow-github-ips-in-azuresql.py script, but when running locally, you will need to open the port to your client IP as indicated in the initial test failure message.

    # Capture the blocked IP from the test failure
TEST_OUTPUT="$(go test -v -tags=conftests -count=1 ./tests/conformance -run=TestStateConformance/azure.sql)"
BLOCKED_IP=$(echo "$TEST_OUTPUT" | grep -Po "Client with IP address '\K[^']*")

# Login to the account with Contributor access to the SQL server instance
az login
az sql server firewall-rule create --resource-group "$AzureResourceGroupName" --server "$AzureSqlServerName" -n "AllowTestClientIP" --start-ip-address "$BLOCKED_IP" --end-ip-address "$BLOCKED_IP"

Running Azure conformance tests via GitHub workflows

  1. Fork the dapr/components-contrib repo.

  2. In your fork on GitHub, add the secrets:

    • AZURE_CREDENTIALS: copy and paste the contents of the AZURE_CREDENTIALS file from the output folder of the script.
    • AZURE_KEYVAULT: copy and paste the value of the AzureKeyVaultName variable from the *-conf-test-config.rc file in the output folder of the script. This is usually of the form <prefix>-conf-test-kv where the prefix string is the user name portion of the Azure account UPN by default, or the value specified using the --prefix parameter when running the script.

  3. Under the Actions tab, enable the "Components Conformance Tests" workflow and manually trigger the workflow.

Tearing down Azure resources after use

Run the teardown <prefix>-teardown-conf-test.sh script generated to the output path for setup-azure-conf-test.sh. Using the defaults from the setup example, this would be:

az login
az account set -s "Name of Test Deployment Subscription"
~/azure-conf-test/myazurealias-teardown-conf-test.sh

⚠ This will delete the resource group containing all the resources, remove the service principals that were created and purge the test Key Vault. Purging the Key Vault is not a recoverable action, so do not run this script if you have modified it for other purposes.