Skip to content

Document sharing configuration across a subset of applications (GH-618)#3250

Open
won-seoop wants to merge 1 commit into
spring-cloud:mainfrom
won-seoop:doc-618-sharing-common-properties
Open

Document sharing configuration across a subset of applications (GH-618)#3250
won-seoop wants to merge 1 commit into
spring-cloud:mainfrom
won-seoop:doc-618-sharing-common-properties

Conversation

@won-seoop

Copy link
Copy Markdown

Summary

Closes GH-618

The Config Server documentation only covers the base application.properties case, which is shared with all applications. Users who want to share configuration among a subset of applications (e.g., only services that use Cassandra, Redis, etc.) had no documented approach.

The Spring Cloud maintainer already answered the question in the issue thread ("Might be nice to add to the docs") but the answer was never added to the reference documentation.

Changes

Added a new [[sharing-configuration-across-applications]] section to client.adoc (placed between "Locating Remote Configuration Resources" and "Requesting Multiple Labels") that explains:

  • Setting spring.cloud.config.name to a comma-separated list (e.g., ${spring.application.name},cassandra) to load additional shared config files
  • The resulting property source load order with an example (application, application-{profile}, servicea, servicea-{profile}, cassandra, cassandra-{profile})
  • An [IMPORTANT] callout noting that name order matters — later names override earlier ones

Test plan

  • Verify AsciiDoc renders correctly
  • Confirm the new section appears between the two existing sections in rendered output

🤖 Generated with Claude Code

…g-cloudGH-618)

Add a new 'Sharing Configuration Across Applications' section to the
client docs explaining how to use a comma-separated list for
spring.cloud.config.name to opt individual services into shared
configuration files (cassandra.properties, redis.properties, etc.)
without polluting application.properties which is loaded by all apps.

Document the load order and property override precedence (later names
take precedence over earlier names).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Document howto share common properties for a subset of services

2 participants