configuration plans can be marked as unrequired
keathley opened this issue · comments
File and remote configuration should be able to be marked as unrequired. This would mean that we wouldn't block the startup sequence but would still allow us to watch those sources for changes. This allows us to not block startup of the app based on an external connection but still allows us to issue changes this way once vapor is able to connect to these systems. For instance we may not want to force vapor to block until we can connect to ETCD, but if its able to connect to etcd once its running we want to be able to use etcd to issue configuration changes.