Skip to content
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

[Docs]: conflicting behaviour for storage autoscaling for RDS #41063

Closed
Kurtyjlee opened this issue Jan 24, 2025 · 7 comments · Fixed by #41167
Closed

[Docs]: conflicting behaviour for storage autoscaling for RDS #41063

Kurtyjlee opened this issue Jan 24, 2025 · 7 comments · Fixed by #41167
Labels
documentation Introduces or discusses updates to documentation. service/rds Issues and PRs that pertain to the rds service.
Milestone

Comments

@Kurtyjlee
Copy link
Contributor

Documentation Link

https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/db_instance

Description

max_allocated_storage - (Optional) When configured, the upper limit to which Amazon RDS can automatically scale the storage of the DB instance. Configuring this will automatically ignore differences to allocated_storage. Must be greater than or equal to allocated_storage or 0 to disable Storage Autoscaling.

To enable Storage Autoscaling with instances that support the feature, define the max_allocated_storage argument higher than the allocated_storage argument. Terraform will automatically hide differences with the allocated_storage argument value if autoscaling occurs.

In the docs, it says to max_allocated_storageallocated_storage || max_allocated_storage == 0 to disable storage autoscaling, however, in another part of the documentation, it says it will enable storage autoscaling. Is this discrepancy expected? if not, what should the actual behaviour be?

References

No response

Would you like to implement a fix?

Yes

@Kurtyjlee Kurtyjlee added the documentation Introduces or discusses updates to documentation. label Jan 24, 2025
Copy link

Community Note

Voting for Prioritization

  • Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
  • Please see our prioritization guide for information on how we prioritize.
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

  • If you are interested in working on this issue, please leave a comment.
  • If this would be your first contribution, please review the contribution guide.

@github-actions github-actions bot added the needs-triage Waiting for first response or review from a maintainer. label Jan 24, 2025
@justinretzolk
Copy link
Member

Hey @Kurtyjlee 👋 Thank you for taking the time to raise this! I had to re-read the documentation a couple of times (further proving your point that it should be more clear), however, this seems to be a matter of the last sentence of the max_allocated_storage argument's documentation being a bit clumsy. There are three possibilities with regards to the argument:

  1. Not defined: Does not enable autoscaling, necessary for DB instances that don't support autoscaling
  2. Defined as greater than or equal to allocated_storage: Enable autoscaling for the DB instance
  3. Defined as 0: Explicitly disable autoscaling for DB instances that support it

Would rewording that last sentence as follows make this more clear?

Must be greater than or equal to allocated_storage to enable Storage Autoscaling, or set to 0 to disable Storage Autoscaling for instances that support it.

@justinretzolk justinretzolk added waiting-response Maintainers are waiting on response from community or contributor. service/rds Issues and PRs that pertain to the rds service. labels Jan 27, 2025
@Kurtyjlee
Copy link
Contributor Author

Hey @justinretzolk, thank you for clarifying! That rewording definitely makes it clearer. Would it be okay if I went ahead and submitted a PR to implement this change?

@github-actions github-actions bot removed the waiting-response Maintainers are waiting on response from community or contributor. label Jan 28, 2025
@justinretzolk
Copy link
Member

I'm glad that made sense @Kurtyjlee! If you're up for raising a pull request for this, please feel free to! I try to keep up with documentation pull requests and get them merged as quick as I can, but feel free to tag me in and I'll get it reviewed.

@justinretzolk justinretzolk removed the needs-triage Waiting for first response or review from a maintainer. label Jan 30, 2025
@Kurtyjlee
Copy link
Contributor Author

Hi @justinretzolk I have created the PR here, requesting your review!

Copy link

Warning

This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them.

Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.

@github-actions github-actions bot added this to the v5.85.0 milestone Jan 31, 2025
Copy link

github-actions bot commented Feb 3, 2025

This functionality has been released in v5.85.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Introduces or discusses updates to documentation. service/rds Issues and PRs that pertain to the rds service.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants