r/aws_evidently_segment

[GlennChia]

Description

New Resource for CloudWatch Evidently Segment.

Relations

Relates #22624

References

• API_CreateSegment
• API_DeleteSegment
• API_GetSegment

Note: Only Segment tags can be updated at the moment

Output from Acceptance Testing

$ make testacc TESTARGS='-run=TestAccEvidentlySegment' PKG=evidently
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/evidently/... -v -count 1 -parallel 20  -run=TestAccEvidentlySegment -timeout 180m
=== RUN   TestAccEvidentlySegment_basic
=== PAUSE TestAccEvidentlySegment_basic
=== RUN   TestAccEvidentlySegment_description
=== PAUSE TestAccEvidentlySegment_description
=== RUN   TestAccEvidentlySegment_tags
=== PAUSE TestAccEvidentlySegment_tags
=== RUN   TestAccEvidentlySegment_disappears
=== PAUSE TestAccEvidentlySegment_disappears
=== CONT  TestAccEvidentlySegment_basic
=== CONT  TestAccEvidentlySegment_tags
=== CONT  TestAccEvidentlySegment_disappears
=== CONT  TestAccEvidentlySegment_description
--- PASS: TestAccEvidentlySegment_disappears (21.71s)
--- PASS: TestAccEvidentlySegment_basic (28.11s)
--- PASS: TestAccEvidentlySegment_description (28.15s)
--- PASS: TestAccEvidentlySegment_tags (65.95s)
PASS
ok      github.com/hashicorp/terraform-provider-aws/internal/service/evidently  66.049s

...

[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.

[ewbankkit]

LGTM 🚀.

% make testacc TESTARGS='-run=TestAccEvidentlySegment_' PKG=evidently ACCTEST_PARALLELISM=2
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/evidently/... -v -count 1 -parallel 2  -run=TestAccEvidentlySegment_ -timeout 180m
=== RUN   TestAccEvidentlySegment_basic
=== PAUSE TestAccEvidentlySegment_basic
=== RUN   TestAccEvidentlySegment_description
=== PAUSE TestAccEvidentlySegment_description
=== RUN   TestAccEvidentlySegment_patternJSON
=== PAUSE TestAccEvidentlySegment_patternJSON
=== RUN   TestAccEvidentlySegment_tags
=== PAUSE TestAccEvidentlySegment_tags
=== RUN   TestAccEvidentlySegment_disappears
=== PAUSE TestAccEvidentlySegment_disappears
=== CONT  TestAccEvidentlySegment_basic
=== CONT  TestAccEvidentlySegment_tags
--- PASS: TestAccEvidentlySegment_basic (25.42s)
=== CONT  TestAccEvidentlySegment_patternJSON
--- PASS: TestAccEvidentlySegment_patternJSON (23.89s)
=== CONT  TestAccEvidentlySegment_description
--- PASS: TestAccEvidentlySegment_tags (61.54s)
=== CONT  TestAccEvidentlySegment_disappears
--- PASS: TestAccEvidentlySegment_description (24.45s)
--- PASS: TestAccEvidentlySegment_disappears (17.41s)
PASS
ok  	github.com/hashicorp/terraform-provider-aws/internal/service/evidently	85.621s

[ewbankkit]

@GlennChia Thanks for the contribution 🎉 👏.

[github-actions]

This functionality has been released in v4.38.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.