is it possible that this value is being predefined when the flow is built/registered and thus not using the most up to date value (the one at flow execution time)?
n
nicholas
10/13/2021, 8:38 PM
Hi @Kyle McChesney - I think you’re correct that those values are being determined at registration and not execution time; try moving that import into the task itself. So long as the
settings.py
file is importable within the docker image you should be able to get the correct env values
Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.