They will introduce a breaking change on April 8th. This will NOT affect your WeWeb apps in production. However, it may affect your experience working inside the WeWeb Editor.
To ensure the Supabase plugin continues to work correctly in the WeWeb Editor, you need to update your plugin configuration.
Make sure to add a Service Role Key to your Supabase plugin settings:
As implied in the “What’s next?” section of this GitHub discussion, the service role key could also be deprecated soon.
This GitHub discussion describes how Supabase generally plans to remove any legacy keys in the near future, which would include the service role key. Are there plans to migrate to “Publishable and secret API keys” before this happens?
There are no firm plans yet but we’re in touch with the Supabase team and monitoring the situation to ensure there are no disruptions to our services and WeWeb apps in production
I have lost all connection to Supabase, and the new interface does not work. I have a copy of my project with a plugin of the old type, and now that doesn’t work either, so I am actually 100% stuck…
I was just about to update my info.
The underlying problem has been solved.
It was a reference to a tenant in Supabase that had been deleted, but was still present in some cached info. So when I recreated it, I got it to work.
But the issue with the WeWeb Data & API interface remains.
When a connection has been created, it is not possible to check or edit settings, and it can not be deleted. You can only work from tables onwards.
If you create a connection by mistake, it remains in your project forever.
But my main problem was solved in Supabase. It took me two days, because everything looked perfect on the surface…
