change: postgres.resources.storage.capacity #3190

Hello,
due to our recent change to organizations based billing we have decided to make postgres.resources.storage.capacity mandatory in your nhost.toml. Up until now we were relying on your plan to select a default value when you were missing that setting but because organizations may support multiple projects and you may want to spread the free allowance amongst them we have decided that it is better to always provision projects with 1GB and let you decide if you want to upgrade the capacity of your project or assign it to different projects.

Unfortunately this means that deployments missing that block will trigger an error. If you see an error indicating that storage resources is null or missing, please, add the following block to your nhost.toml:

[postgres.resources.storage]
capacity = ???

Replace ??? with your current capacity, which you can find here; https://app.nhost.io/orgs/_/projects/_/settings/database

For more information about the motivation behind this change, please, read the following section in our docs

Thanks for your understanding and apologies for the inconvenience.