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

Neptune - support storage type #34984

Closed
sagitsofan opened this issue Dec 19, 2023 · 3 comments · Fixed by #34985
Closed

Neptune - support storage type #34984

sagitsofan opened this issue Dec 19, 2023 · 3 comments · Fixed by #34985
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/neptune Issues and PRs that pertain to the neptune service.
Milestone

Comments

@sagitsofan
Copy link
Contributor

sagitsofan commented Dec 19, 2023

Description

AWS Neptune released the new I/O–Optimized storage type feature, we need to add support both on the cluster level and db instance level:

storage_type: iopt1/standard

See more info here:
https://docs.aws.amazon.com/neptune/latest/userguide/storage-types.html#provisioned-iops-storage
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/neptune_cluster

Affected Resource(s) and/or Data Source(s)

aws_neptune_cluster
aws_neptune_cluster_instance

Potential Terraform Configuration

No response

References

No response

Would you like to implement a fix?

No

@sagitsofan sagitsofan added the enhancement Requests to existing resources that expand the functionality or scope. label Dec 19, 2023
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.

@terraform-aws-provider terraform-aws-provider bot added the needs-triage Waiting for first response or review from a maintainer. label Dec 19, 2023
@sagitsofan sagitsofan changed the title AWS Neptune - support storage type AWS Neptune - support new storage type Dec 19, 2023
@sagitsofan sagitsofan changed the title AWS Neptune - support new storage type Neptune - support new storage type Dec 19, 2023
@sagitsofan sagitsofan changed the title Neptune - support new storage type Neptune - support storage type Dec 20, 2023
@ewbankkit ewbankkit added service/neptune Issues and PRs that pertain to the neptune service. and removed needs-triage Waiting for first response or review from a maintainer. labels Jan 10, 2024
@github-actions github-actions bot added this to the v5.32.0 milestone Jan 11, 2024
Copy link

This functionality has been released in v5.32.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!

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 Feb 13, 2024
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/neptune Issues and PRs that pertain to the neptune service.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants