From f9ef8941419e1f6007b7d0f51dcf3146271d839c Mon Sep 17 00:00:00 2001 From: Brad Warren Date: Sat, 31 Jul 2021 19:15:01 -0700 Subject: [PATCH] update snapcraft.cfg comment (#8959) --- .azure-pipelines/templates/stages/deploy-stage.yml | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/.azure-pipelines/templates/stages/deploy-stage.yml b/.azure-pipelines/templates/stages/deploy-stage.yml index abbb1fd1a..4ae4c563e 100644 --- a/.azure-pipelines/templates/stages/deploy-stage.yml +++ b/.azure-pipelines/templates/stages/deploy-stage.yml @@ -19,11 +19,12 @@ stages: # Then the file was added as a secure file in Azure pipelines # with the name snapcraft.cfg by following the instructions at # https://docs.microsoft.com/en-us/azure/devops/pipelines/library/secure-files?view=azure-devops - # including authorizing the file in all pipelines as described at - # https://docs.microsoft.com/en-us/azure/devops/pipelines/library/secure-files?view=azure-devops#how-do-i-authorize-a-secure-file-for-use-in-all-pipelines. + # including authorizing the file for use in the "nightly" and "release" + # pipelines as described at + # https://docs.microsoft.com/en-us/azure/devops/pipelines/library/secure-files?view=azure-devops#q-how-do-i-authorize-a-secure-file-for-use-in-a-specific-pipeline. # # This file has a maximum lifetime of one year and the current - # file will expire on 2021-07-28 which is also tracked by + # file will expire on 2022-07-25 which is also tracked by # https://github.com/certbot/certbot/issues/7931. The file will # need to be updated before then to prevent automated deploys # from breaking.