From b9c1746abf269bf7a1956d1d0a9bfa11d15840fb Mon Sep 17 00:00:00 2001
From: Gary Verhaegen <gary.verhaegen@digitalasset.com>
Date: Wed, 4 Nov 2020 12:42:23 +0100
Subject: [PATCH] add env vars back to azure-cron (#7882)

Looks like I was wrong and [secret variables] do indeed require
explicit mapping:

[secret variables]: https://docs.microsoft.com/en-us/azure/devops/pipelines/process/variables?view=azure-devops&tabs=yaml%2Cbatch#secret-variables

> Unlike a normal variable, they are not automatically decrypted into
> environment variables for scripts. You need to explicitly map secret
> variables.

CHANGELOG_BEGIN
CHANGELOG_END
---
 azure-cron.yml | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/azure-cron.yml b/azure-cron.yml
index b2a06ed0ba..d12fd6e930 100644
--- a/azure-cron.yml
+++ b/azure-cron.yml
@@ -102,6 +102,14 @@ jobs:
               echo "Done."
             fi
           done
+        env:
+          DOCKER_LOGIN: $(DOCKER_LOGIN)
+          DOCKER_PASSWORD: $(DOCKER_PASSWORD)
+          DOCKER_CONTENT_TRUST_KEY: $(DOCKER_CONTENT_TRUST_KEY)
+          DOCKER_CONTENT_TRUST_USERNAME: $(DOCKER_CONTENT_TRUST_USERNAME)
+          # Does not appear explicitly in the script, but is used by
+          # docker trust key load
+          DOCKER_CONTENT_TRUST_REPOSITORY_PASSPHRASE: $(DOCKER_CONTENT_TRUST_REPOSITORY_PASSPHRASE)
       - template: ci/tell-slack-failed.yml
 
   - job: vscode_marketplace