/ai Flows in windmill allows you to have a static inputs viewer that just shows all static inputs used in the flow so you can easily set them and also have a global overview of them, we want to change it now by instead having an environnement variables setter which that in place of static input now the user would set env key=value, and by doing so allow it to be referenced (e.g FOO is a global env variable with a value that has been set in the global env variable manager now located at where was the static input viewer), it means that we should now store the global env variable too in the flow definition, and maybe caching it once in memory to not have to pull it from db again and again, an example of how it should works is by reusing the PropPickerWrapper by updating it too now also take the env object so it can have it context like he can have the flow result and the flow input so now we can use bound the value to one of the env variables like the other. Request made by @dieriba
/ai Flows in windmill allows you to have a static inputs viewer that just shows all static inputs used in the flow so you can easily set them and also have a global overview of them, we want to change it now by instead having an environnement variables setter which that in place of static input now the user would set env key=value, and by doing so allow it to be referenced (e.g FOO is a global env variable with a value that has been set in the global env variable manager now located at where was the static input viewer), it means that we should now store the global env variable too in the flow definition, and maybe caching it once in memory to not have to pull it from db again and again, an example of how it should works is by reusing the PropPickerWrapper by updating it too now also take the env object so it can have it context like he can have the flow result and the flow input so now we can use bound the value to one of the env variables like the other. Request made by @dieriba