From 61e35223e4e842b04b78d892a158993640510606 Mon Sep 17 00:00:00 2001 From: Piero Toffanin Date: Wed, 17 Nov 2021 15:14:55 -0500 Subject: [PATCH] Created Updating Snapcraft STORE_LOGIN secret (markdown) --- Updating-Snapcraft-STORE_LOGIN-secret.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 Updating-Snapcraft-STORE_LOGIN-secret.md diff --git a/Updating-Snapcraft-STORE_LOGIN-secret.md b/Updating-Snapcraft-STORE_LOGIN-secret.md new file mode 100644 index 0000000..a1475e4 --- /dev/null +++ b/Updating-Snapcraft-STORE_LOGIN-secret.md @@ -0,0 +1,15 @@ +Store Login +In order to upload to the store, the action requires login credentials. Rather than a user name and password, the action expects the data produced by the snapcraft export-login command. + +As well as preventing the exposure of the password, it also allows the credentials to be locked down to only the access the action requires: + +$ snapcraft export-login --snaps=PACKAGE_NAME \ --acls package_access,package_push,package_update,package_release \ exported.txt + +This will produce a file exported.txt containing the login data, which should be a multi-line file starting with [login.ubuntu.com]. The credentials can be restricted further with the --channels and --expires arguments if desired. + +In order to make the credentials available to the workflow, they should be stored as a repository secret: + +choose the “Settings” tab. +choose “Secrets” from the menu on the left. +click “Add a new secret”. +set the name to STORE_LOGIN (or whatever is referenced in the workflow), and paste the contents of exported.txt as the value. \ No newline at end of file