Nathan Wallace

Note: also adds the aliases and is_enrolled fields to the User table

Improvements to web form display when input has already been responded to

1

Here is what I see for a simple button input: Changes I'd suggest: * Keep the original prompt. * Disable the buttons * Show a yellow warning alert above the...

Can I use a param as a default for another param in a pipeline?

1

I'd like to do this: ``` pipeline "approve" { param "prompt" { default = "Do you approve?" } param "subject" { default = param.prompt } // ... } ``` But...

Triggers should support params

1

When creating a trigger in a mod it would be great to have the ability to specify parameters. Currently, the only option to provide information to a trigger is through...

File watching does not detect change inside loop block of input step?

1

Version: v0.4.3-rc.2 I have this step: ```hcl step "input" "approve" { notifier = notifier[param.approvers[0]] type = "button" subject = param.subject prompt = param.prompt option "approve" { label = "Approve" style...

null JSON value not visible in output on dark mode terminal

4

Here is what I see: Here is the actual text copied out: ``` [approve] Output result = { "label": "Skip", "style": null, "value": "skip" } ```

Consider this pipeline with a step that is always skipped: ```hcl mod "local" { title = "flowpipe-mod-issues" } pipeline "dependencies_should_not_be_run" { step "transform" "foo" { if = false value =...

I'm trying to use `throw { ... }` and `error { ... }` inside a step (combined with `for_each`). It's difficult to debug what's happening right now though - the...

I have a `for_each` loop for an input step. I'd like to run them in parallel, but stop waiting for inputs if any of them get a specific response (e.g....

I'm trying to use an input step in a pipeline. I'd like to have the subject be optional in my pipeline as well (so it will default to use the...