Peter Demin

This could work, but I have following concerns: 1. Whether environment extrapolation is used or not should be more explicit. Currently, if kibitzr-creds.yml has `password: ${ PASSWORD }` but `yamlenv`...

I checked if I could document desired behavior: https://kibitzr.readthedocs.io/en/latest/configuration.html#environment-variables Most of it is actually working, the only remaining part is yamlenv in `kibitzr-creds.yml`.

@thisHermit, I reviewed the state of this issue. Here is an updated description: Support for environment variables doesn't need to go into a separate extension as stated in the original...

I know it was original idea to have this switch in kibitzr.yml. But now I see, that it’s a bad idea. Let me elaborate. We have 3 sources of configuration:...

So the plan is: 1. Load creds using yamlenv unconditionally. 2. Add safe_load support to yamlenv. 3. Replace load with safe_load in creds loader.

Hi! Thanks for input, it helps prioritize further development. What about configuration? Should it leave in cloud storage too? Or pull from private repo? I personally don't trust cloud providers...

That would be awesome!

I would be a great feature once implemented. I'm not sure if two schedulers will cooperate. I would try to use `entry.next()` to add a new single point for `schedule`.

I like your idea. However I think, it should go under a different key: `schedule` (instead of `period`). Then, if both `schedule` and `period` are present, both should be used....

Yes, I want to leave `period` as is. From the language point, `period: 5 minutes` is more readable than `schedule: 5 minutes`. YAML won't allow having multiple `schedule` keys, but...