spring.config.name is not formatted as an environment variable in multi-page reference documentation

[sahrawat]

Here is the quote from https://docs.spring.io/spring-boot/docs/current/reference/html/spring-boot-features.html#boot-features-external-config-application-property-files

If you use environment variables rather than system properties, most operating systems disallow period-separated key names, but you can use underscores instead (for example, spring.config.name instead of spring.config.name).

I suppose it should be spring_config_name.

I wasn't really sure how to do this so I created an issue anyways. Guide me for the future so I don't create useless issues.

[philwebb]

I wasn't really sure how to do this so I created an issue anyways. Guide me for the future so I don't create useless issues.

This is the correct place to raise issues like this. It's certainly not a useless issue, so thanks for raising it!

[philwebb]

Looks like this is an issue with out asciidoc macro.

[philwebb]

Oddly this only appears in the /html output, /htmlsingle is fine.

[wilkinsona]

This comment from @mojavelinux seems relevant to our problem, specifically this part:

When the format is long, the attributes are parsed if the content model is ":attributes". If the content model is ":text", then the value between the brackets is stored in the "text" attribute. In other words, when the format is long, the attributes map is always populated. But the attributes aren't parsed unless the content model is ":attributes" (the default).

It's from 2016, but assuming things are still the same, it would suggest that when the multi-page documentation is being rendered, the content model is :text but when the single-page documentation is being rendered it's :attributes.

[wilkinsona]

I think I may have a fix for this: spring-io/spring-asciidoctor-extensions#51