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

set value inside aws_dynamodb_table_item #7729

Closed
bitdivine opened this issue Feb 26, 2019 · 2 comments
Closed

set value inside aws_dynamodb_table_item #7729

bitdivine opened this issue Feb 26, 2019 · 2 comments
Labels
enhancement Requests to existing resources that expand the functionality or scope. stale Old or inactive issues managed by automation, if no further action taken these will get closed.

Comments

@bitdivine
Copy link

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

AWS dynamodb items are JSON blobs. The AWS API supports setting not just the whole blob but the value at some path within the JSON tree. It would be nice if the terraform table_item resource supported such a path. Using it would express: "this branch of the JSON should have this value".

New or Affected Resource(s)

  • aws_dynamodb_table_item

Potential Terraform Configuration

resource "aws_dynamodb_table_item" "sub_item" {
  table_name = "configs"
  hash_key   = "project_name"
  item = "${data.template_file.template.rendered}" # This is JSON as usual
  path = ["somekey", "anotherkey"]                         # This is new: It describes where inside the item the JSON should be placed.
}

References

@bitdivine bitdivine added the enhancement Requests to existing resources that expand the functionality or scope. label Feb 26, 2019
@github-actions
Copy link

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

@github-actions github-actions bot added the stale Old or inactive issues managed by automation, if no further action taken these will get closed. label Feb 15, 2021
@ghost
Copy link

ghost commented Apr 17, 2021

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!

@ghost ghost locked as resolved and limited conversation to collaborators Apr 17, 2021
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. stale Old or inactive issues managed by automation, if no further action taken these will get closed.
Projects
None yet
Development

No branches or pull requests

1 participant