Closed brendt closed 3 days ago
Here is a diagram of how we will try and set this up. The goal will be to eliminate the chicken and egg problem with the bootstrappers where they are discovering config files, but need the app config to work.
@brendt - One thing we've talked about in the past is decoupling discovery from the Tempest container. A specific example I can think of where that might be useful is a minimal console application, a non-Tempest application using the command/event bus, etc. To confirm, you are not wanting to do that?
To confirm, you are not wanting to do that?
I confirm, I do not want to do that :p
Related: #365 , #366
I'd say it's good enough for now.
Moving bootstraps to application level and cleaning things up, including config discovery