Rahul Mehta04/14/2023, 1:35 AM
or flyte remote)? We'd like to inject some metadata from CI into the workflow application code (in a way that labels or annotations don't immediately solve) We could theoretically hack around this by using the downward API to mount
as a volume, but being able to directly set env var(s) seems more idiomatic/breaks fewer abstractions. Curious if anyone else has had to deal with this
Dan Rammer (hamersaw)04/14/2023, 1:08 PM
of a workflow execution. This would allow a user to set envvars during workflow execution (UI / flytectl / pyflyte) or on the launchplan. These envvars are then set on every container that Flyte starts. Does this sound like what you're looking for? Currently, these PRs won't be merged for awhile, but maybe it makes sense to refactor this bit out and get it merged relatively quickly.
Rahul Mehta04/14/2023, 1:09 PM
env var but this sounds like it's exactly it