aws_dynamodb_table resource reading tags from dynamodb-local throws UnknownOperationException

[hashibot]

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

• The initial plan works as expected but the apply errors when refreshing state. It does appear to create the tables and stores them in the tfstate file but you are unable to plan or apply any changes after that initial apply.
  The output is here: https://gist.github.com/cstavro/d9d3686454fafd2d95a6ebc7cba43363

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

• provider/aws: Add tag support to the dynamodb table resource terraform#11617

[freedomofkeima]

Is there any progress with this issue? 👀

[farmbytes]

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

[jeffski]

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

[radeksimko]

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.

[stefansundin]

Fixed in #6149

[ghost]

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!