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]: Cannot use attr.Value basetypes.StringValue in aws_elasticache_reserved_cache_node #39451

Closed
joesteffee opened this issue Sep 23, 2024 · 6 comments · Fixed by #39945
Closed
Assignees
Labels
bug Addresses a defect in current functionality. regression Pertains to a degraded workflow resulting from an upstream patch or internal enhancement. service/elasticache Issues and PRs that pertain to the elasticache service.
Milestone

Comments

@joesteffee
Copy link

Terraform Core Version

1.9.5

AWS Provider Version

5.68.0

Affected Resource(s)

aws_elasticache_reserved_cache_node

Expected Behavior

aws elasticache nodes should reserve

Actual Behavior

reserved node is not created

Relevant Error/Panic Output Snippet

│ Error: Value Conversion Error
│
│   with module.elasticache-ephemeral.aws_elasticache_reserved_cache_node.redis[0],
│   on modules/elasticache/main.tf line 64, in resource "aws_elasticache_reserved_cache_node" "redis":
│   64: resource "aws_elasticache_reserved_cache_node" "redis" {
│
│ An unexpected error was encountered trying to convert into a Terraform value. This is always an error in the provider. Please report the
│ following to the provider developer:
│
│ Cannot use attr.Value basetypes.StringValue, only types.RFC3339Duration is supported because types.rfc3339DurationType is the type in the
│ schema

Terraform Configuration Files

data "aws_elasticache_reserved_cache_node_offering" "example" {
  cache_node_type     = "cache.t4g.small"
  duration            = "P1Y"
  offering_type       = "No Upfront"
  product_description = "redis"
}

resource "aws_elasticache_reserved_cache_node" "example" {
  reserved_cache_nodes_offering_id = data.aws_elasticache_reserved_cache_node_offering.example.offering_id
  id                               = "optionalCustomReservationID"
  cache_node_count                 = 3
}

Steps to Reproduce

Attempt to reserve an elasticache node

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

No response

Would you like to implement a fix?

None

@joesteffee joesteffee added the bug Addresses a defect in current functionality. label Sep 23, 2024
@github-actions github-actions bot added the service/elasticache Issues and PRs that pertain to the elasticache service. label Sep 23, 2024
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 Sep 23, 2024
@Toubi01
Copy link

Toubi01 commented Oct 4, 2024

Functionality was introduced in #29832.
Having the same issue still in AWS Provider Version 5.70.0.

@pshen
Copy link

pshen commented Oct 21, 2024

Faced the same issue in the AWS Provider Version 5.72.1

Error output

  │ Error: Value Conversion Error
  │ 
  │   with module.elasticache_redis_cluster_ssl.aws_elasticache_reserved_cache_node.rcn["rcn-redis-2024-10-21"],
  │   on ../../dci-elasticache-redis-tfmodule/elasticache_redis_cluster_reserved_cache_nodes.tf line 8, in resource "aws_elasticache_reserved_cache_node" "rcn":
  │    8: resource "aws_elasticache_reserved_cache_node" "rcn" {
  │ 
  │ An unexpected error was encountered trying to convert into a Terraform
  │ value. This is always an error in the provider. Please report the following
  │ to the provider developer:
  │ 
  │ Cannot use attr.Value types.RFC3339Duration, only basetypes.StringValue is
  │ supported because basetypes.StringType is the type in the schema

The new functionality wasn't tested properly.

@justinretzolk justinretzolk added regression Pertains to a degraded workflow resulting from an upstream patch or internal enhancement. and removed needs-triage Waiting for first response or review from a maintainer. labels Oct 29, 2024
@terraform-aws-provider terraform-aws-provider bot added the prioritized Part of the maintainer teams immediate focus. To be addressed within the current quarter. label Oct 29, 2024
@jar-b jar-b self-assigned this Oct 31, 2024
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.75.0 milestone Oct 31, 2024
@github-actions github-actions bot removed the prioritized Part of the maintainer teams immediate focus. To be addressed within the current quarter. label Nov 11, 2024
Copy link

This functionality has been released in v5.75.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 Dec 16, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Addresses a defect in current functionality. regression Pertains to a degraded workflow resulting from an upstream patch or internal enhancement. service/elasticache Issues and PRs that pertain to the elasticache service.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants