-
Notifications
You must be signed in to change notification settings - Fork 1
Warn of about to expire snap branches.
License
canonical/snap-expire
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Folders and files
| Name | Name | Last commit message | Last commit date | |
|---|---|---|---|---|
Repository files navigation
This repository's CI will daily broadcast snaps branches soon to expire in
Mattermost's ~branch-expirations channel.
As the Snap Store considers that information is private data, to enroll
your snaps here, you first need to gather authorization data.
The recipe to enroll your snaps is:
* Locally, "snap install surl".
* Locally,
$ surl -e {your@snapstore.email} -p package_access -s production --snap {snap} -a {auth-file}
You will be asked your password and 2FA.
This causes your authentication identifier file {auth-file}.surl, used in next
step, to be created.
You can provide multiple --snap arguments if you prefer to generate an
unified {auth-file}.surl.
* Copy the contents of ~/snap/surl/common/{auth-file}.surl to a new repository
secret in https://github.com/canonical/snap-expire/settings/secrets/actions.
* Add your printf line and env line to .github/workflows/ci.yaml.
* Append your entry to watched-snaps, whose format is
{snap} {expire-in} {auth-file} [{mattermost-ids}]
{expire-in}: Your snap (and optionally mattermost-ids for pinging) will be
included in the Mattermost's reminder message if a branch of it
will expire in {expire-in} days.
{mattermost-ids}: List of Mattermost IDs to ping (separated by whatever
punctuation, but not spaces, e.g. person1:person2,person3).
About
Warn of about to expire snap branches.