Drazen Sander

> FYI: as mentioned in [the docs](https://hop.apache.org//manual/latest/workflow/actions/start.html), the repeat options in the Start action are mainly there for historical reasons. Hi, thanks for the link. Does that mean it's unlikely...

@sramazzina It would also be great if the option were available for Docker as well.

Hi @sramazzina, The current Apache Hop Docker image already provides `HOP_ENVIRONMENT_CONFIG_FILE_NAME_PATHS`. This variable allows you to specify a comma separated list of config file paths. To avoid picking those files...

Hi @sramazzina, very good point, i hadn't considered that at all. The only thing that comes to my mind is that, when adapting the environment, there could be an option...

Hi @hansva, I tested whether I can use the variable resolver to read an SQL file and then use it directly in the Table Input step. However, it turns out...

Hi @hansva, i have a question regarding the feature request. **What behavior exactly did you have in mind?** If we introduce the variables ```bash ENV HOP_PARENT_PROJECT_NAME= ENV HOP_PARENT_PROJECT_CONFIG_FILE_NAME=parent-project-config.json ENV HOP_PARENT_PROJECT_FOLDER=...

> So like a parameter. I like the idea but have mixed feelings about the transparency and complexity to implement the parsing algorithm for nested variable expressions. Perhaps `#{default-resolver:VARIABLE_NAME:default}` could...

> Never close the ones with "mixed feelings", they are usually the most interesting. But if we want default values, perhaps we can add another semi-colon option to ALL resolvers...

What would be the pros and cons of the two options?

If that’s the case, I would suggest NOT using the variable-based approach. An extension could still be added later if the community deems it necessary