Skip to content

Support ephemeral ports in dev services config #48784

@holly-cummins

Description

@holly-cummins

This is a recent regression. It used to work, but stopped working, presumably as a result of the test classloading rewrite.

I've spotted this for Lambda, but it's a bigger issue and will need some rework of the config source and priorities.

If config is set to "0", we should lazily override the value in the config source so that the real value could override the hardcoded "0" in the application properties. This a nicer approach than what the extension used to have to do, which is put the new config into system properties as a hand-rolled override.

The problem is that if the priority of the dynamic config is too high, it takes precedence over the TestResourceLifeCycleManager config used in some tests. Parts of the test talk to the managed resource, part to the dev service, and it's chaos.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Status

    In Progress

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions