Commit Graph

7 Commits

Author SHA1 Message Date
Jared Tobin
5fc506c837
meta: bump janeway version in glob action
Uses janeway v0.13.3, which allows us to remove some of the hacky steps
in the glob action entrypoint script introduced in 17f3431b43.
2021-01-12 13:51:19 +04:00
Jared Tobin
17f3431b43
meta: glob action tweaks
Sets two environment variables, LANDSCAPE_STREAM and
LANDSCAPE_SHORTHASH, to be employed by landscape builds.  Also reverts
the janeway version used to v0.13.1 as the --dev flag is unnecessary.
2021-01-06 03:40:46 +04:00
Jared Tobin
1f7e454a90
meta: use janeway v0.13.2 in glob action 2021-01-05 20:32:56 +04:00
Jared Tobin
d6e21e1519
meta: invoke janeway with --dev
The --dev flag injects a development modal in Landscape when globbing.
2021-01-05 19:15:14 +04:00
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