-
Notifications
You must be signed in to change notification settings - Fork 2
Remove config override tests after service startup when using config provider #172
Comments
For the services listed, environment variable overrides will not be applied:
Here is an example:
|
In order to run the services without the config provider, the services should have the full set of configurations (local and common) available to them. The default service configuration files only include the local config. We should either inject the common config parts into the same file, or point to the common config file via the respective common config environment variable override. The latter is currently being implemented; see edgexfoundry/go-mod-bootstrap#487. The common config file is available at https://github.com/edgexfoundry/edgex-go/blob/main/cmd/core-common-config-bootstrapper/res/configuration.yaml. It can be sourced from the edgexfoundry snap or for quick/manual testing directly from github. |
An example of making service run without config provider:
|
The behavior of core-data has changed compared to its previous version:
|
@MonicaisHer please report the bug at https://github.com/edgexfoundry/go-mod-bootstrap |
@farshidtz sure, reported: edgexfoundry/go-mod-bootstrap#494 |
As expected by #4448, the snap tests have started failing since this change because the overrides no longer apply on top of configurations coming from config provider:
Common configuration loaded from the Configuration Provider. No overrides applied
Need to change the snap tests to no longer test that, or make the services run without config provider.
Failing test result:
The text was updated successfully, but these errors were encountered: