Inconsistent usage of application configuration
Someone on Gitter was following this tutorial and got confused by the fact the project does not contain an application.yml. Most of the tutorial is using application.properties and only a few places are using yaml.
Considering the default is properties perhaps the few parts that were written with YAML can be harmonized so that only properties is used. We can, of course, add a note about the YAML support if that's necessary.
Some of the projects in this guide use Zuul, and the route configuration looks much better IMO in YAML, so I think we should keep it that way. I'd be more than happy to clarify that in the text if you can point at the original source of confusion more precisely.
the route configuration looks much better IMO in YAML
I don't disagree with that but if a user follows the guide and don't know about this, this is super confusing to have 90% of the example with one format and the minority with others. There is no real explanation about it either so this may just as well be two totally different files for a newcomer.
The only section I found is this:
Starting from the blank Initializr application, we add the Spring Session dependency (like in the UI above). The Gateway is ready to run, but it doesn’t yet know about our backend services, so let’s just set that up in its application.yml (renaming from application.properties if you did the curl thing above):
The renaming applies to every way the app is created by initializr (IDE, web UI, command line) so I don't really understand why this text focuses on curl. If you want to stick with YAML then I'd argue everything should have this format. My preference would be properties all the way with a note about YAML