Configuration defaults about celos HOT 4 CLOSED

👍

Additionally, I think it'd be a good place to start enforcing some consistent conventions for things like workflow naming so that they're easier to grok downstream as well. For example: define the application name, data bucket/window UTC timestamp that it's running against, maybe a list of input and output paths, and some sort of additional "notes" or userdata field and then force the actual name of the workflow when it's run to be something like "[${data_bucket_timestamp}] ${application_name} : ${userdata} <${input_paths} => ${output_paths}>"

That specific example is possibly a bit verbose for just the name, but you get the idea. Right now there isn't much consistency in terms of how the actual workflow instance names come up. Some have timestamps, some don't, those that do don't always include them the same way, etc, etc.

from celos.

Could probably use https://github.com/typesafehub/config

from celos.

I’m very happy with Typesafe config, it has no dependencies and is very flexible.

from celos.

Yeah, @christophsturm mentioned you were using it, so that's why I looked into it.

from celos.