You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can see some cases that inheriting envvars from the worker-manager host node will be a good idea, that would allow devices to have some customizability that might be useful for distributed systems yet still managed centrally (same IoT sensor everywhere, but a tag is manually set on each sensor with it's location name, etc...), thinking it could be any combination of the follow:
envvar with some sort of prefix (IE NEBULA_)
file with a list of the envvars
not sure about how to handle multiple apps each getting different envvars yet, anyone got any ideas in that regards?
The text was updated successfully, but these errors were encountered:
A really simple soultion that was staring me in the face & I somehow missed is to use parse_it and to have it have a dict of all worker inherited key:values in the following format:
I can see some cases that inheriting envvars from the worker-manager host node will be a good idea, that would allow devices to have some customizability that might be useful for distributed systems yet still managed centrally (same IoT sensor everywhere, but a tag is manually set on each sensor with it's location name, etc...), thinking it could be any combination of the follow:
not sure about how to handle multiple apps each getting different envvars yet, anyone got any ideas in that regards?
The text was updated successfully, but these errors were encountered: