I'd like to focus on getting feedback on the part of your proposal where
- we treat a collection of env vars under a shared prefix as textual
pipeline options
- every SDK has compatible parsing of the option names and values
Beyond that, most use cases should use their own namespace prefix
Hi guys,
this is a followup of the thread on the pipeline options from system
properties discussion
the context of this new thread is adding portability into the game and
therefore if we want a common and shared way to create pipeline options
from the environment
since it impacts
