-
Notifications
You must be signed in to change notification settings - Fork 4.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve documentation for azurerm_postgresql_server storage_mb #7475
Comments
Hi @thomas-riccardi, so what happens right now if you define storage_mb + autogrow_enabled and exceed limit defined in storage_mb is:
So from my opinion you should define either auto_grow_enabled or storage_mb but not both. If you feel there is a lack in documentation, contributions are always welcome 👍 |
Hi @NickMetz, I'm not sure I understand your scenario:
It seem If my understanding is correct, then indeed we should not use autogrow and storage_mb at the same time, but AFAIK it's not documented anywhere. (And there is then no way to ask for an initial disk size: what is the initial disk size?) |
This senario was described above:
Yes, storage_mb is not a cap. It's the provisioned storage.
[Workaround] If you want to provision a postgres database server with initial storage size it's possible to use ignore_changes
Inital azure postgres server has 5 GB disk storage
|
Thank you @NickMetz, it's all clear now! And thanks for the workaround with ignore_changes. (In fact the Azure service documentation could be improved too). Hopefully this ticket will help people before the documentation includes all that. |
Community Note
Description
azurerm_postgresql_server
storage_mb
documentation saysMax storage allowed for a server.
, it does not say what happens with storage Autogrow enabled:1.
is what I understand from reading the documentation (and coming from GCP world)2.
is what I understand from the portal UI: we cannot move the cursor below the specified value instorage_mb
.New or Affected Resource(s)
References
The text was updated successfully, but these errors were encountered: