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]: Regression: 5.53.0 not working with DynamoDB Local #37921

Closed
agrzegorczyk-leonsoftware opened this issue Jun 11, 2024 · 4 comments · Fixed by #37924
Closed

[Bug]: Regression: 5.53.0 not working with DynamoDB Local #37921

agrzegorczyk-leonsoftware opened this issue Jun 11, 2024 · 4 comments · Fixed by #37924
Assignees
Labels
bug Addresses a defect in current functionality. service/dynamodb Issues and PRs that pertain to the dynamodb service. tags Pertains to resource tagging.
Milestone

Comments

@agrzegorczyk-leonsoftware
Copy link

agrzegorczyk-leonsoftware commented Jun 11, 2024

Terraform Core Version

1.8.5

AWS Provider Version

5.53.0

Affected Resource(s)

aws_dynamodb_table

Expected Behavior

pass terraform apply

Actual Behavior

Stops with error because DynamoDB Local not supports tag-related operations.

Relevant Error/Panic Output Snippet

│ Error: listing tags for DynamoDB Table (arn:aws:dynamodb:ddblocal:000000000000:table/kvstore): operation error DynamoDB: ListTagsOfResource, https response error StatusCode: 400, RequestID: acde0f12-8b91-4464-baa6-8d76a19c6510, api error UnknownOperationException: Tagging is not currently supported in DynamoDB Local.
│ 
│   with aws_dynamodb_table.kvstore,
│   on table.tf line 1, in resource "aws_dynamodb_table" "kvstore":
│    1: resource "aws_dynamodb_table" "kvstore" {

Terraform Configuration Files

terraform {
  required_providers {
    aws   = "= 5.53.0"
  }
}

provider "aws" {
  endpoints {
    dynamodb = "http://127.0.0.1:8001"
  }
  alias                       = "local"
  access_key                  = "mock"
  region                      = "us-east-1"
  secret_key                  = "mock"
  skip_credentials_validation = true
  skip_metadata_api_check     = true
  skip_requesting_account_id  = true
}

resource "aws_dynamodb_table" "kvstore" {

  provider = aws.local

  name         = "kvstore"
  billing_mode = "PAY_PER_REQUEST"
  hash_key     = "key"

  attribute {
    name = "key"
    type = "S"
  }
}

Steps to Reproduce

docker run -it --rm -p 8001:8000 amazon/dynamodb-local:2.4.0
terraform init
terraform apply --auto-approve

Debug Output

No response

Panic Output

No response

Important Factoids

This in fact is reopen of #37463, because it seems that changes from #37472 didn't help.
The last version this works was 5.48.0.

References

No response

Would you like to implement a fix?

None

@agrzegorczyk-leonsoftware agrzegorczyk-leonsoftware added the bug Addresses a defect in current functionality. label Jun 11, 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 service/dynamodb Issues and PRs that pertain to the dynamodb service. label Jun 11, 2024
@terraform-aws-provider terraform-aws-provider bot added the needs-triage Waiting for first response or review from a maintainer. label Jun 11, 2024
@ewbankkit ewbankkit added tags Pertains to resource tagging. and removed needs-triage Waiting for first response or review from a maintainer. labels Jun 11, 2024
@ewbankkit ewbankkit self-assigned this Jun 11, 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 Jun 11, 2024
@ewbankkit ewbankkit assigned ewbankkit and unassigned ewbankkit Jun 11, 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.54.0 milestone Jun 11, 2024
@github-actions github-actions bot removed the prioritized Part of the maintainer teams immediate focus. To be addressed within the current quarter. label Jun 14, 2024
Copy link

This functionality has been released in v5.54.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 Jul 15, 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. service/dynamodb Issues and PRs that pertain to the dynamodb service. tags Pertains to resource tagging.
Projects
None yet
2 participants