Andrzej Ludwikowski

Actually, a lot of samples use WebClient in tests, and I have some second thoughts about changing this. For instance, it might be surprising to see the `ComponentClient` in tests...

Can't you just use transition without the input: 

Unfortunately not. Here is everything that could be part of the description: https://github.com/git-commit-id/git-commit-id-maven-plugin/blob/master/docs/git-describe.md In that case, maybe we could give some hints to the users in docs/pom.xml samples with a...

Yeah, we could clarify that users can apply different versioning/tagging strategies and slightly warn the timestamp might not be a good idea for production setup.

I'm open to all options. For sure we need to provide a way to configure the application in some (Spring-like) way for the code first SDK.

If we are comfortable enough that the solution with docker-compose works for us to run the app, I don't see any reason to not use it for integration tests. Option...

Ok, this is the current state: I agree that the user function VE span will be always (?) very small, it should be at least, so it's not very useful...

I'm not sure if merging kalix endpoint with VE span is a good idea. If we are ok with what we have at this point, I would postpone this decision,...

Somehow related to this discussion, the runtime will retry in the case of a subscription failure, and a new span will be created. Is that what we want to show?

Not really, I can prepare a small app to reproduce the issue.