Silent Test Failure - SpringCloudConfigServer_DiscoveryFirst_ReturnsExpectedDefaultData

[TimHess]

This integration test requires both a config server and a service registry, and the config server needs to be registered with the registry.

Without failFast=true this test was "passing" even though the above pre-requisites weren't met. #515 skips the test and sets this property so that we'll have a more accurate representation of what's happening when the pre-requisites can be met. Use this issue as a reminder to enhance the docker image and un-skip the test

[jkonicki]

The config server image needs to be enhanced to work with discovery first

[bart-vmware]

@TimHess What's needed to get this resolved? We now have a config-server image that supports discovery, but the cibuild doesn't start a Eureka instance. I wonder if it should, as it may take several minutes for Eureka to refresh, which is impractical.

[TimHess]

I would think Eureka would be ready in <60 seconds, but we'll have to see what actually happens in the CI environment. We could add the command to start Eureka as the first step in the jobs (at least for component builds) to help mitigate the startup time

I think it's just removing the skip and making sure the Config server start command has -e eureka.client.enabled=true added