Extend / Eject story with SST ION

[amir-ziaei]

Hello,

I've recently been exploring SST (ION engine) and find it to be a fantastic tool. However, as I consider integrating it into a work-related project, I have some concerns which I'm hoping to hear the team's response to.

Extendability

Is there a plan in place for handling scenarios where some infra components are not yet supported by SST? Could you provide insights into how you expect the consumer to address such gaps? Are there any plans on your end to implement a plugin interface to extend support for additional components?

Ejectablity

In the event that a user wishes to discontinue using SST, is there a means to access the underlying IoC that SST manages? How easy would that be?

---

Looking forward to hearing from the team!
Thanks!

[san4d]

Not part of the team but am using Ion and used v2.

All SST components are Pulumi components, so the "lock in" is with Pulumi. In my project, I'm using both SST components and Pulumi components together seamlessly. When there isn't a prebuilt component, I drop down and write my own Pulumi component.

If I wanted to move off of SST, I would reimplement each of the crafted SST components myself as Pulumi components (and have to figure out SDLC things, like a replacement for live lambda). If I wanted to move off of Pulumi, that would be a larger task. You can always look at your cloud provider to see the exact resources created. I recommend doing this anyhow.

https://ion.sst.dev/docs/components/

[jayair]

Yeah @san4d basically covered it all, I would add that the extend path when Ion does not support it is:

• Try, the transform: https://ion.sst.dev/docs/components/#transform
• Then try Pulumi directly
• If not supported by Pulumi but there's a TF provider, then there are steps to generate a Pulumi component as well, we do this ourselves in some cases: https://github.com/sst/pulumi-supabase