Skip to content

Allow embedded config server to be disabled  #1431

Closed

Description

@scottfrederick

When embedding Config Server in an application, it should be possible to disable loading configuration from an external source unless the app deployer explicitly defines an EnvironmentRepository configuration (e.g. in a bootstrap.yml file provided in a spring.cloud.bootstrap.location outside of the deployed application jar file).

Currently this is difficult to do. If no configuration is provided, the default is to use a git repository but this will fail to load because a spring.cloud.config.server.git.uri is required. You can provide a native repository with a dummy location as a default, but this must be done with a composite type to allow alternative repositories to override this default.

Activity

  1. yashdotdev13 commented on Oct 29, 2026

    @yashdotdev13
    Contributor

    I have opened PR #3365 to address this issue.

    The change introduces the spring.cloud.config.server.default-repository.enabled property, allowing the default Git environment repository to be disabled when set to false, while preserving the existing behavior by default.

    I have also added a test to verify that the default repository is not created when disabled.

  2. added this to the 5.1.0-RC2 milestone on Oct 30, 2026
  3. moved this from In Progress to Done in 2026.0.0-RC2on Oct 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions