-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
Resolves issue while creating DynamoDB items #14075
Resolves issue while creating DynamoDB items #14075
Conversation
Bump |
Bumping again. |
what would it take to get this pushed and versioned! my tables have "." in their keys |
Pull request #21306 has significantly refactored the AWS Provider codebase. As a result, most PRs opened prior to the refactor now have merge conflicts that must be resolved before proceeding. Specifically, PR #21306 relocated the code for all AWS resources and data sources from a single We recognize that many pull requests have been open for some time without yet being addressed by our maintainers. Therefore, we want to make it clear that resolving these conflicts in no way affects the prioritization of a particular pull request. Once a pull request has been prioritized for review, the necessary changes will be made by a maintainer -- either directly or in collaboration with the pull request author. For a more complete description of this refactor, including examples of how old filepaths and function names correspond to their new counterparts: please refer to issue #20000. For a quick guide on how to amend your pull request to resolve the merge conflicts resulting from this refactor and bring it in line with our new code patterns: please refer to our Service Package Refactor Pull Request Guide. |
@edwardofclt Thanks for this PR, I'm really looking forward for it to be merged into TF Provider AWS. Could you please take a look into resolving conflicts (so that it's not an obstacle once Provider maintainers get to this PR). Thank you. |
return names | ||
} | ||
|
||
func cleanDynamoDbKeyName(key string) string { | ||
reg, err := regexp.Compile("[^a-zA-Z]+") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I couldn't find what is the exact constraint for the key name. Is it sort of "the key name must start with alpha char only" (rather than "alphanumeric")? If yes, could you please point me in the right direction in the AWS DynamoDB documentation? Thanks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you 🎉
% make testacc TESTS=TestAccDynamoDBTableItem PKG=dynamodb
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/dynamodb/... -v -count 1 -parallel 20 -run='TestAccDynamoDBTableItem' -timeout 180m
--- PASS: TestAccDynamoDBTableItem_wonkyItems (25.03s)
--- PASS: TestAccDynamoDBTableItem_withMultipleItems (25.12s)
--- PASS: TestAccDynamoDBTableItem_rangeKey (26.64s)
--- PASS: TestAccDynamoDBTableItem_basic (26.82s)
--- PASS: TestAccDynamoDBTableItem_updateWithRangeKey (36.22s)
--- PASS: TestAccDynamoDBTableItem_update (39.42s)
PASS
ok github.com/hashicorp/terraform-provider-aws/internal/service/dynamodb 40.690s
This functionality has been released in v4.9.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! |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Community Note
Closes #10385
Release note for CHANGELOG:
Output from acceptance testing: