Open solidcell opened 1 year ago
This would be super helpful. Interesting how this is a thing for actions, but not for runFlow/runScript. As pointed above, having to type the same path on several files is quite cumbersome. I was trying to create an output.paths for a while before coming here and seeing it's not a thing already. Sad
Is your feature request related to a problem? Please describe. In order to dry usage of nested flows, I'd like to define constants for their paths. However, parameters don't seem to work when used for
runFlow.file
.For instance:
$ export MAESTRO_EMAIL_LOGIN_SUBFLOW=/path/to/subflows/email-login.yaml
Note: I'm using a leading
/
so that the path isn't interpreted as a relative path. Ostensibly, this wouldn't be necessary if interpolation worked, since it would see there's already a leading/
.Describe the solution you'd like I'd like for the above to interpolate correctly. However, it looks like interpolation doesn't occur. The text is taken literally.
I get a failure with the following error message:
Flow file is invalid: /${MAESTRO_SUBFLOW_EMAIL_LOGIN}
The documentation doesn't go into specifics about where interpolation is permitted, but from the examples and my experimentation, it seems like it only works on top-level nodes.
Not only would I like this to work in order to keep my flow files DRY and less verbose, but they are much too coupled with the directory structure otherwise. For instance, if I have the following structure:
Then in
feature.yaml
I need to reference the subflow via../../subflows/email-login.yaml
The flow file shouldn't need to know internally where it lives. And I'd argue it shouldn't need to know where a subflow files lives either. If I change the directory structure of my flow files in the future, even just a little, it will case a lot of pain.Describe alternatives you've considered