properties in application.yml are not loaded about spring-cloud-consul

[spencergibb]

I did have to put spring.cloud.consul.port in bootstrap.yml because s-c-consul-config uses the bootstrap context. spring.cloud.consul.config.enabled=false didn't work (in bootstrap). That issue has been fixed in 90dfce5. Otherwise, I'm unable to reproduce your issue. Do you have a project you can share that duplicates the problem?

[derylseale]

I think you can reproduce the issue just using the sample application provided in spring-cloud-consul-sample. If you add spring.cloud.consul.config.enabled: false to the application.yml file, rebuild and package per the instructions, and re-launch the JAR file, you'll see that it still tries to connect to a running consul agent.

[spencergibb]

I was using the sample app. spring.cloud.consul.config.enabled=false does work in bootstrap.yml (not application.yml) after my fix. Other properties are also working.

[derylseale]

So do all the consul related properties have to be specified in bootstrap.yml? The documentation only mentions application.yml.

[spencergibb]

If you use Consul Config, the values under spring.cloud.consul.config.* and the connection information spring.cloud.consul.{host|port} do. The docs have been updated to reflect that here 2a019ec.