What’s the difference between integrating Sentry in Fly vs integrating it with the Sentry SDKs?
Is automatic release tagging still planned? Otherwise I would need to roll my own via GitHub Actions.
Integrating with Fly is more convenient, and comes with a year’s worth of credits. Otherwise, there isn’t much difference until we integrate more features like deploy tracking.
We don’t have immediate plans for this. But, integrating via Actions sounds like a good intermediate solution. If you do that, we could learn from your example and add to our flyctl action.
Are there any plans to allow adding users to Sentry without Fly SSO?
Not all users who would need access to Sentry need access to Fly, on the contrary the plan is to keep Fly access limited to only our most senior engineers.
Its quite a pitty really if we cannot take advantage of the free year in Sentry just because we want a more secure setup for our Fly account. Realistically it could make the difference between choosing Sentry over another service. Because if we are paying we are going to look into all out options, but if we get a free year of Sentry that cost savings adds up for a new startup like us and is enough to choose them.
That’s the say nothing of our position against the use of SSO in general.
Is there any way to disable this? We already have a Sentry org and we have nodes running on Fly but also other clouds and need a central sentry server.
We’re noticing that our calls to sentry are not working on the fly nodes and I’m guessing it’s because of this?