From ee845dd6ed778648332e2aa991c535de03d1699d Mon Sep 17 00:00:00 2001 From: Brad Warren Date: Tue, 6 Sep 2022 14:08:20 -0700 Subject: [PATCH] update credential info --- .azure-pipelines/templates/stages/deploy-stage.yml | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/.azure-pipelines/templates/stages/deploy-stage.yml b/.azure-pipelines/templates/stages/deploy-stage.yml index 8144f4bee..e60908134 100644 --- a/.azure-pipelines/templates/stages/deploy-stage.yml +++ b/.azure-pipelines/templates/stages/deploy-stage.yml @@ -13,7 +13,7 @@ stages: # credential file was created by running: # # snapcraft logout - # snapcraft export-login --channels=beta,edge snapcraft.cfg + # snapcraft export-login --channels=candidate,beta,edge snapcraft.cfg # (provide the shared snapcraft credentials when prompted) # # Then the file was added as a secure file in Azure pipelines @@ -23,11 +23,9 @@ stages: # 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 2023-06-17 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. + # This file has a maximum lifetime of one year and the current file will + # expire on 2023-09-06. The file will need to be updated before then to + # prevent automated deploys from breaking. # # Revoking these credentials can be done by changing the password of the # account used to generate the credentials. See