Creating [s3] section triggers errors by inserting ALL envvars from your env to s3client • Although some products use this sideeffect (backward compatibility problem) ◦ COMMON_PARAM=3 python main.py [TaskA] a=1 [TaskB] b=2 TaskA(a=1, common_param=3) TaskB(b=2, common_param=3)
So let’s reconstruct this. How much backward compatibility will be broken? • poor: retain current • better: not default, but %(envvar)s works ◦ current PR • best: just use ${envvar}