Storage in terraform is not working

[groovyjovy]

Chore

Describe the chore

Hi, I am deploying an application using terraform

Looking at the implementation, the part that reads and manipulates the config regarding Storage does not seem to exist
Also, the config is commented out in the test
Looking the terraform documentation and the Network link is broken, but it is implemented internally. However, Storage has a broken link and is not implemented.
Is there a reason for these? If there is none in particular, it seems to me that the documentation should be revised so as not to cause confusion.
Also, upon further investigation, it seems that the develop branch of the Supabase CLI defines a structure for reading configs related to Storage, etc. Using this, I was able to modify the Supabase Storage configuration in my local environment using terraform. I have already implemented this feature locally and can contribute a PR if you're interested!

This is my first Issue against OSS. Sorry for my poor English.
Thanks for your great product!

[shellscape]

I started my own provider since this one seems abandoned. Check it out here https://github.com/shellscape/terraform-provider-supabase

[sweatybridge]

Hi @shellscape, it's true that our teams are overwhelmed atm but we are still keen to maintain the official terraform provider. Would you be interested to contribute to the provider through our open collective program? I think it's better for our community to focus development efforts on one codebase.

If you are keen, or know someone who is, feel free to fill out this form and I will be happy to follow up.

[shellscape]

@sweatybridge given the pretty low frequency of maintenance from the supabase team (that's not a dig, just fact based on commit history and issue/PR followup) I'm not inclined to contribute here if there's going to be a lengthy delay in review and follow up on contributions - we (my team) simply have to move at a faster pace.

I have a pretty lengthy and well-documented history of open source maintenance and you're likely using some of my packages, or packages I maintain, on a daily basis if you're working with node. If you'd like to invite me as a maintainer without a bunch of red tape and formalities, I'm happy to help steer the repository. Otherwise I'm content to keep working on my solution separately. You are of course welcome to draw from my project as it's MIT, if you'd prefer to keep this repo gated.