This commit enables PR's to run inegration tests by relying on keys with
only the necessary permissions to run on CI workloads
Signed-off-by: Marcos Lilljedahl <marcosnils@gmail.com>
All new projects are created as "locked" by default so this allow their
deployment. Additionally, a moreh helpful error message is added when
NETLIFY_ACCOUNT cannot be found
Fixes#1918
Signed-off-by: Marcos Lilljedahl <marcosnils@gmail.com>
The todoapp example contains a Netlify plan which uses the latest dagger
additions: do & Client API. We are thinking of merging the examples
repository into this one to make working with this easier. This is a
step in that direction.
We are not using the yarn package so that we can revert
https://github.com/dagger/dagger/pull/1673 without breaking this
implementation.
The GitHub Action is WIP, we will continue with that tomorrow:
https://github.com/dagger/dagger-for-github/issues/24
Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
* Script is written to filesystem, not inlined as argument
* Pass script either as string, or directory+filename
Signed-off-by: Solomon Hykes <solomon@dagger.io>
* `cmd` is renamed to `command` for readability
* `script` is removed. Feature moves up the stack (bash.#Run,
python.#Run)
Signed-off-by: Solomon Hykes <solomon@dagger.io>
This change "collapses" together log "groups" containing hidden fields
for the TTY logger.
e.g. `actions.foo._a` and `actions.foo_b` will show up as a combined `actions.foo`.
Caveats: Since we don't know in advance how many tasks are in a group, the state will change back and forth.
For each task in a group, the state will transition from computing to complete (e.g. blue to green), then back to computing and so on.
The transition is fast enough not to be visibile.
Signed-off-by: Andrea Luzzardi <aluzzardi@gmail.com>
