Emanuele Capparelli

I would say use the existing one. If nothing changed in the configuration, the only thing that should be updated is the code.

As an update, my "workaround" for now is to set "async_resources": false, so that it doesn't create a new SNS subscription (the old one stays in place).

Related to #10956

Link to the LaunchDarkly integration framework PR: https://github.com/launchdarkly/integration-framework/pull/14 And the related docs: https://github.com/launchdarkly/LaunchDarkly-Docs/pull/254

> Proposing we remove the ability to directly sign up for Self-Host (Self-Serve) and Self-Host Enterprise. Get started would link to PostHog Cloud signup page, and from there, we'd offer...

>@kappa90 - this was a winning variant in a previous experiment we ran (I believe?) so I presume we'll have an onboarding flow that gets card details early. Yes, [about...

> My point is less about the homepage positioning than the fact the line between "the platform" and "the products" feels ill-defined. This wireframe doesn't communicate to me these are...

@pjhul could you take a look at why this is failing? Seems unrelated to this PR

We can close this one as @benjackwhite has been working on a different approach

@mariusandra not sure why but one hogQL production test didn't match the API, see where I removed `hasMore` from the test.