Sébastien Crocquesel

@gsmet could be closed

@gsmet could be closed

I guess there is a misunderstanding on who's who. `io.quarkiverse.amazonservices:quarkus-amazon-lambda` is the quarkus wrapper around the [lambda client](https://sdk.amazonaws.com/java/api/latest/software/amazon/awssdk/services/lambda/LambdaClient.html) from the [aws sdk](https://github.com/aws/aws-sdk-java-v2) to manage lambda while `io.quarkus:quarkus-amazon-lambda` is the extension...

@gsmet I'm revamping quickstarts to use DevServices, eliminating the need for Docker CLI. This can be closed.

We do have a similar issue but it seems argo-cd is trying to create event in the target cluster/namespace with its service account token and not the token configured in...

After digging, the issue is because the `LogResourceEvent` create an event in the cluster the server is running in. Thus ResourceRef of ResourceNode is meaningless to this cluster. `logResourceEvent` should...

I pushed #12796 to fix argocd was not using the correct cluster config. But I don't know if the clusterrole should still be modified.

> Hm. I think it makes sense to create the resource events on the Argo CD host cluster. Maybe the resource ref should just be changed to point to the...

@luneo7 @galderz Thank you for the analysis. I would prefer not to disable linking at build time. Additionally, it seems that SNS is also necessary. In most cases (telemetry without...

I opened a discussion quarkusio/quarkus#40573 as we have a similar use case in an another extension and I guess it deserves a little more thinking about the user experience.