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

Closes #38753.
Closes #39844.

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! 😃

[ewbankkit]

LGTM 🚀.

% make testacc TESTARGS='-run=TestAccDynamoDBKinesisStreamingDestination_' PKG=dynamodb ACCTEST_PARALLELISM=2
make: Verifying source code with gofmt...
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go1.23.2 test ./internal/service/dynamodb/... -v -count 1 -parallel 2  -run=TestAccDynamoDBKinesisStreamingDestination_ -timeout 360m
2024/10/23 12:16:06 Initializing Terraform AWS Provider...
=== RUN   TestAccDynamoDBKinesisStreamingDestination_basic
=== PAUSE TestAccDynamoDBKinesisStreamingDestination_basic
=== RUN   TestAccDynamoDBKinesisStreamingDestination_approximateCreationDateTimePrecision
=== PAUSE TestAccDynamoDBKinesisStreamingDestination_approximateCreationDateTimePrecision
=== RUN   TestAccDynamoDBKinesisStreamingDestination_disappears
=== PAUSE TestAccDynamoDBKinesisStreamingDestination_disappears
=== RUN   TestAccDynamoDBKinesisStreamingDestination_Disappears_dynamoDBTable
=== PAUSE TestAccDynamoDBKinesisStreamingDestination_Disappears_dynamoDBTable
=== CONT  TestAccDynamoDBKinesisStreamingDestination_basic
=== CONT  TestAccDynamoDBKinesisStreamingDestination_disappears
--- PASS: TestAccDynamoDBKinesisStreamingDestination_disappears (53.81s)
=== CONT  TestAccDynamoDBKinesisStreamingDestination_approximateCreationDateTimePrecision
--- PASS: TestAccDynamoDBKinesisStreamingDestination_basic (61.46s)
=== CONT  TestAccDynamoDBKinesisStreamingDestination_Disappears_dynamoDBTable
--- PASS: TestAccDynamoDBKinesisStreamingDestination_approximateCreationDateTimePrecision (55.03s)
--- PASS: TestAccDynamoDBKinesisStreamingDestination_Disappears_dynamoDBTable (52.87s)
PASS
ok  	github.com/hashicorp/terraform-provider-aws/internal/service/dynamodb	119.626s

% make testacc TESTARGS='-run=TestAccFirehoseDeliveryStream_basic\|TestAccFirehoseDeliveryStream_iceberg' PKG=firehose
make: Verifying source code with gofmt...
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go1.23.2 test ./internal/service/firehose/... -v -count 1 -parallel 20  -run=TestAccFirehoseDeliveryStream_basic\|TestAccFirehoseDeliveryStream_iceberg -timeout 360m
2024/10/23 14:33:05 Initializing Terraform AWS Provider...
=== RUN   TestAccFirehoseDeliveryStream_basic
=== PAUSE TestAccFirehoseDeliveryStream_basic
=== RUN   TestAccFirehoseDeliveryStream_icebergUpdates
    delivery_stream_test.go:1011: Unresolvable Glue permission issue
--- SKIP: TestAccFirehoseDeliveryStream_icebergUpdates (0.00s)
=== CONT  TestAccFirehoseDeliveryStream_basic
--- PASS: TestAccFirehoseDeliveryStream_basic (160.11s)
PASS
ok  	github.com/hashicorp/terraform-provider-aws/internal/service/firehose	165.175s

[ewbankkit]

@rob93c @sonya Thanks for the contribution 🎉 👏.

[github-actions]

This functionality has been released in v5.73.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!

[github-actions]

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.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.