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 (like KENN_PIPELINEOPTIONS_*) so let's not get distracted by the idea of using this for global defaults. Kenn On Fri, Feb 16, 2018 at 8:59 AM, Romain Manni-Bucau <[email protected]> wrote: > 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 java+go+python(+other potential coming languages) it is > important to gather the feedback of everyones about it. > > The proposal can be to use to read the environment variable to use: > > BEAM_* or beam.* as a prefix (case insentive?) and remove this prefix for > the actual key > > ex: export BEAM_appName=myapp or export beam.appName=myapp > > any opinion on that? > > Romain Manni-Bucau > @rmannibucau <https://twitter.com/rmannibucau> | Blog > <https://rmannibucau.metawerx.net/> | Old Blog > <http://rmannibucau.wordpress.com> | Github > <https://github.com/rmannibucau> | LinkedIn > <https://www.linkedin.com/in/rmannibucau> | Book > <https://www.packtpub.com/application-development/java-ee-8-high-performance> >
