Terraform-provider-aws: aws_dynamodb_table resource reading tags from dynamodb-local throws UnknownOperationException

Created on 13 Jun 2017  ·  6Comments  ·  Source: hashicorp/terraform-provider-aws

_This issue was originally opened by @cstavro as hashicorp/terraform#11926. It was migrated here as part of the provider split. The original body of the issue is below._


Terraform Version

0.8.6

Affected Resource(s)

  • aws_dynamodb_table

Terraform Configuration Files

provider "aws" {
  region = "us-east-1"
  dynamodb_endpoint = "http://localhost:8000"
}

resource "aws_dynamodb_table" "mytable" {
  name = "mytable"
  read_capacity = 1
  write_capacity = 1
  hash_key = "id"

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

Debug Output

https://gist.github.com/cstavro/5e23b233ebfc29ffa48e5ead52d27c34

Expected Behavior

  • Should be able to plan and apply a config
  • Should be able to plan after an apply

Actual Behavior

Steps to Reproduce

  1. terraform apply

Important Factoids

  • This works fine in v0.8.5
  • Running latest version of dynamodb-local for development

References

Pretty sure this is the guy that causes the problem

bug servicdynamodb upstream

Most helpful comment

+1 to fix this. Table gets created but can't be destroyed

All 6 comments

Is there any progress with this issue? 👀

Any updates? I am still seeing this issue with Terraform v0.10.3

aws_dynamodb_table.basic-dynamodb-table: UnknownOperationException: An unknown operation was requested.
    status code: 400

+1 to fix this. Table gets created but can't be destroyed

Closing as a duplicate of #1059 to keep the discussion in a single place. Feel free to follow that issue by subscribing to it or upvoting it.

Thanks.

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

Was this page helpful?
0 / 5 - 0 ratings