Manu

Results 10 comments of Manu

It would be great if this is going to be merged. This would need to be also made available to `client.containers.create` according to the API specs

I'm using `spring-cloud-starter-task` version `3.0.2` and still get this error no matter if i specify `spring.cloud.task.transaction-manager` or not. I have to inject a `PlatformTransactionManager` in my step methods and it...

Any solution to this? I'm still having two transaction managers only because I have Spring Cloud Dependencies in my app. This breaks all of my `@Transactional` methods.

@kewne I think it is because take a look at https://github.com/fmbenhassine/spring-cloud-task/blob/e4581420b04e872f8aac4cb3ad8bab62bbe9c941/spring-cloud-task-core/src/main/java/org/springframework/cloud/task/configuration/SimpleTaskAutoConfiguration.java The TransactionManager Bean is annotated with `Conditional(NoTransactionManagerProperty.class)` So, i am 100% sure I have this property in my `application.yml`....

How come this hasnt been fixed in *4 years*???

As far as i know the only possibility right now is to use network.connect(container, aliases=[])

*bump* i would love to see this feature in future release