Add approximate_creation_date_time_precision to aws_dynamodb_kinesis_streaming_destination

[rob93c]

Description

Add approximate_creation_date_time_precision to aws_dynamodb_kinesis_streaming_destination resource to be able to set a timestamp precision (only accepted values are either MILLISECOND or MICROSECOND).

References

EnableKinesisStreamingConfiguration API documentation

Output from Acceptance Testing

% make testacc TESTS=TestAccDynamoDBKinesisStreamingDestination_ PKG=dynamodb
TF_ACC=1 go1.22.4 test ./internal/service/dynamodb/... -v -count 1 -parallel 20 -run='TestAccDynamoDBKinesisStreamingDestination_'  -timeout 360m
=== RUN   TestAccDynamoDBKinesisStreamingDestination_basic
=== PAUSE TestAccDynamoDBKinesisStreamingDestination_basic
=== RUN   TestAccDynamoDBKinesisStreamingDestination_disappears
=== PAUSE TestAccDynamoDBKinesisStreamingDestination_disappears
=== RUN   TestAccDynamoDBKinesisStreamingDestination_Disappears_dynamoDBTable
=== PAUSE TestAccDynamoDBKinesisStreamingDestination_Disappears_dynamoDBTable
=== CONT  TestAccDynamoDBKinesisStreamingDestination_basic
=== CONT  TestAccDynamoDBKinesisStreamingDestination_Disappears_dynamoDBTable
=== CONT  TestAccDynamoDBKinesisStreamingDestination_disappears
--- PASS: TestAccDynamoDBKinesisStreamingDestination_Disappears_dynamoDBTable (60.38s)
--- PASS: TestAccDynamoDBKinesisStreamingDestination_disappears (60.70s)
--- PASS: TestAccDynamoDBKinesisStreamingDestination_basic (63.30s)
PASS
ok      github.com/hashicorp/terraform-provider-aws/internal/service/dynamodb   64.952s

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this pull request by adding a 👍 reaction to the original post to help the community and maintainers prioritize this pull 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.

For Submitters

• Review the contribution guide relating to the type of change you are making to ensure all of the necessary steps have been taken.
• For new resources and data sources, use skaff to generate scaffolding with comments detailing common expectations.
• Whether or not the branch has been rebased will not impact prioritization, but doing so is always a welcome surprise.

[github-actions]

Welcome @rob93c 👋

It looks like this is your first Pull Request submission to the Terraform AWS Provider! If you haven’t already done so please make sure you have checked out our CONTRIBUTOR guide and FAQ to make sure your contribution is adhering to best practice and has all the necessary elements in place for a successful approval.

Also take a look at our FAQ which details how we prioritize Pull Requests for inclusion.

Thanks again, and welcome to the community! 😃