Derek

Hi @hrithiksawhney, of course! I'll assign it to you.

Can the protos be broken in to a separate PR? Can you link to the promethius API docs for the changes referenced?

Thanks for reporting @pcn

One possible option here is to restrict the bounds of node to below 14 but it would mean anyone running node 14 wouldn't be able to run Clutch. I'm not...

@danielhochman I can't reproduce this. Are you sure you didn't click into the free-form text field and then click continue? Validation should be enforced only on the most recently selected...

Yeah, this was a design choice when we decided to remove the toggle button and add both the free-form input field and schema fields onto the same page. The way...

Pulling this into this weeks sprint for investigation and resolution.

Just an update on this - we landed support for dynamic API resolution in #753 but we would eventually like to have this be configuration driven based on the workflow.

@jpeach would it be helpful to have a note earlier on in the local build guide around requiring node 16?

👍 This seems reasonable. By default we append requested to denote the action is scheduled but not confirmed but there is no reason to force this.