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

[Bug]: expected storage_type to be one of [standard gp2 io1], got gp3 for RDS storage type #27782

Closed
markvdlaan93 opened this issue Nov 13, 2022 · 3 comments
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/rds Issues and PRs that pertain to the rds service.

Comments

@markvdlaan93
Copy link

Terraform Core Version

1.2.1

AWS Provider Version

4.39.0

Affected Resource(s)

  • aws_db_instance

Expected Behavior

It should be possible to adjust storage_type to gp3.

Actual Behavior

expected storage_type to be one of [standard gp2 io1], got gp3

Relevant Error/Panic Output Snippet

No response

Terraform Configuration Files

resource "aws_db_instance" "this" {
  ......
  storage_type = "gp3"
  ......
}

### Steps to Reproduce

Run `terraform plan` on a `aws_db_instance` resource with storage_type value gp3

### Debug Output

_No response_

### Panic Output

_No response_

### Important Factoids

_No response_

### References

https://aws.amazon.com/about-aws/whats-new/2022/11/amazon-rds-general-purpose-gp3-storage-volumes/

### Would you like to implement a fix?

_No response_
@markvdlaan93 markvdlaan93 added bug Addresses a defect in current functionality. needs-triage Waiting for first response or review from a maintainer. labels Nov 13, 2022
@github-actions
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 service/rds Issues and PRs that pertain to the rds service. label Nov 13, 2022
@ewbankkit ewbankkit added enhancement Requests to existing resources that expand the functionality or scope. and removed bug Addresses a defect in current functionality. needs-triage Waiting for first response or review from a maintainer. labels Nov 14, 2022
@ewbankkit
Copy link
Contributor

@markvdlaan93 Thanks for raising this issue.
It has already been noticed in #27702. I'm going to close this one as a duplicate so that we can concentrate discussion in the linked issue.
Please add any additional comments there.

@github-actions
Copy link

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 15, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/rds Issues and PRs that pertain to the rds service.
Projects
None yet
Development

No branches or pull requests

2 participants