Docker compose, expose container details (service connection and others) as application properties about spring-boot HOT 3 CLOSED

I'm afraid not.

The Playtika Testcontainers support depends on Spring Cloud. It uses its bootstrap context (a separate application context that's started very early) to get things up a running and then adds properties to the main context. In terms of the lifecycle and adding properties to the environment, this is similar to what Spring Cloud Config server does.

When designing Spring Boot's service connection support, we didn't want to require a separate application context for bootstrapping, and we had the luxury of being able to avoid that by introducing the ConnectionDetails abstraction. This is lighter weight than requiring another application context, and, as I described above, also has the benefit of allowing the connection details to be accessed in a consistent manner, irrespective of their source.

from spring-boot.

Thanks for the suggestion. Unfortunately, there's a chicken and egg problem here. Properties are used to configure the Docker Compose support so the environment has to have been prepared before the Docker Compose support can run. This makes it too late for that support to then add properties to the environment.

If you want to access the properties that are retrieved from the running containers, you should inject the relevant …ConnectionDetails bean. This will allow the details to be consumed in a consistent way, no matter where they've come from (Docker Compose, Testcontainers, properties in the environment, or a custom …ConnectionDetails bean).

from spring-boot.

@wilkinsona thank you for answering quickly I had considered this I think, I actually wanted to ask why with this request as I'm a curious Spring Boot developer.

I know that in playtika starter they expose new properties after the container is started, isn't it not possible to do it in Spring too?

from spring-boot.