Replies: 2 comments
-
Hi, @tsangste Thanks for the feature request! |
Beta Was this translation helpful? Give feedback.
0 replies
-
Hi, @tsangste |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Checklist
Describe the problem you'd like to have solved
I am deploying my actions, forms and flows from staging to production but after deployment I have to manually edit my actions in production to reference these newly deployed forms due to the forms having a different
form_id
from staging to prod. Also any manual editing would be overwritten when you do another deployment with the cli.Action code:
I would love a way where the
form_id
for forms in actions can be resolved like how flows are done with forms.Describe the ideal solution
As actions are code files I think the best solution would be to leverage action secrets.
By using actions secrets we could basically create a new secret and set the value of the secret to the form name and during processing of the action (would require to change the order so forms complete before actions) we could retrieve the list of forms to resolve the name to ids to replace the secret value with the
form_id
Action Code:
YAML Tenant Config:
Alternatives and current workarounds
No current workaround with cli except for manual editing of actions
Additional context
No response
Beta Was this translation helpful? Give feedback.
All reactions