Azure: Backendless locking connection methods

This setup is only required for backendless mode (no-backend: true).

With the OpenTaco backend/orchestrator, PR locks are stored in the backend database automatically and Azure lock storage configuration is not needed.

How does it work?

There is one mandatory environment variable the user will have to set, in order to use Azure based locks: DIGGER_AZURE_AUTH_METHOD, which can take one of the three values below:

• SHARED_KEY

• CONNECTION_STRING

• CLIENT_SECRET

• MANAGED_IDENTITY

Then, depending on the value of DIGGER_AZURE_AUTH_METHOD, the user will have to set other environment variables.

1. SHARED_KEY

   • DIGGER_AZURE_SA_NAME: Storage account name
   • DIGGER_AZURE_SHARED_KEY: shared key of the storage account

2. CONNECTION_STRING

   • DIGGER_AZURE_CONNECTION_STRING: connection string

3. CLIENT_SECRET

   • DIGGER_AZURE_TENANT_ID: tenant id to use
   • DIGGER_AZURE_CLIENT_ID: client id of the service principal
   • DIGGER_AZURE_CLIENT_SECRET: secret of the service principal
   • DIGGER_AZURE_SA_NAME: storage account name

4. MANAGED_IDENTITY

   • DIGGER_AZURE_SA_NAME: storage account name