Pull back saved runtime variables on trigger edit page

[sugimiyanto]

Is your feature request related to a problem? Please describe.
It's tedious to re-enter runtime variables every time I need to edit a trigger. The previously saved runtime variables are not pulled back on the trigger edit page. I can imagine if I have tens of them.

Describe the solution you'd like
The previous saved runtime variables are pulled back on the trigger edit page.

Describe alternatives you've considered
Manually re-enter all the necessary runtime variables.

Additional context
The previous saved runtime variables:

Runtime variables on trigger edit page are empty.

[johnson-mage]

@sugimiyanto Did you try adding "global variables" in the Pipeline Editor? Those should appear in the "Runtime variables" section when editing a trigger. If your runtime variables (e.g. target_table) were added in the Trigger Edit view at the time you created the trigger and not as a "global" variable, it may not appear under the Runtime variables section when editing the trigger again.

[johnson-mage]

@johnson-mage the "global variables" is constant for a pipeline, isn't it? My pipeline is a generic pipeline which is reusable by multiple triggers to execute different context. The context difference is described in Runtime Variables on each trigger. So, "global variables" is not applicable for this case.

Got it, thanks for clarifying. Will make note of this to improve the UX.

[sugimiyanto]

@johnson-mage the "global variables" is constant for a pipeline, isn't it?
My pipeline is a generic pipeline which is reusable by multiple triggers to execute different context. The context difference is described in Runtime Variables on each trigger.
So, "global variables" is not applicable for this case.

[sugimiyanto]

thanks @johnson-mage