Julien Vey

Sure, this is the high level feature, but we should definitively split the work into multiple (and more simple) issues

I have started to work on a first implementation on this, should have a PR soon

Hi, I was discussing implementation details about this with @gusfcarvalho on Slack, but I should put it here. I have started some work on the implementation of this provider. (https://github.com/external-secrets/external-secrets/pull/1211)...

Hi @gusfcarvalho ! Thank you for your help. There is no extra configuration needed when calling the provider. The only configuration needed is handled with the ExternalSecret resource itself (such...

Hi @gusfcarvalho I still have some minor changes to apply to the PR (TODO comments in the PR description) but I'll be glad if you had time to review it...

+1 to get back this feature. Adding that the workaround in this comment https://github.com/grafana/pyroscope/issues/1186#issuecomment-1169451605 doesn't seem to work anymore. The `POST` request to flamegraph.com is done directly in the user's...

Looks like the code to enable/disable it is till there but I don't see a way to configure it at runtime https://github.com/grafana/pyroscope/blob/main/public/app/util/features.ts#L39

@tpaschalis @simonswine Anything we can do to help move this forward ? I think @hainenber fixed all the previous comment