3 Commits

Author	SHA1	Message	Date
Jared Tobin	daad76b5e2	meta: pull in lfs files when using checkout action ... Some other commits have been squashed in: meta: remove user declarations for glob action This is a tricky problem. SSH needs UID 0 to exist, and intuitively it does (root), but we can't enforce that when GitHub is running our container. Specifying "USER 0:0" in the actions Dockerfile doesn't cut it. Instead it seems best to try and construct a shadow-utils setup on the underlying Docker image. meta: target glob workflow at release/next-js	2020-12-19 13:18:15 -03:30
Jared Tobin	0e2cb45121	meta: don't sequence arguments in glob action defn	2020-12-19 10:46:55 -03:30
Jared Tobin	7b1b4d8cc6	meta: add a 'glob' GitHub action ... This action, when supplied with the appropriate arguments, will create a Landscape glob from GITHUB_SHA [1] and deploy it OTA to the appropriate ship. It needs to be supplied the following: * ship name * base64-encoded GCP Service Account credentials * a base64-encoded SSH secret key to be used for GCP actions * the corresponding base64-encoded SSH public key [1]: https://docs.github.com/en/free-pro-team@latest/actions/reference/environment-variables	2020-12-19 10:30:59 -03:30