-
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
td/Add tests to slot_type and fixes #39353
Conversation
Community NoteVoting for Prioritization
For Submitters
|
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.
LGTM 🎉
Just needs a changelog.
% make testacc PKG=lexv2models TESTS=TestAccLexV2ModelsSlotType_
make: Verifying source code with gofmt...
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go1.22.6 test ./internal/service/lexv2models/... -v -count 1 -parallel 20 -run='TestAccLexV2ModelsSlotType_' -timeout 360m
--- PASS: TestAccLexV2ModelsSlotType_compositeSlotTypeSetting (42.88s)
--- PASS: TestAccLexV2ModelsSlotType_valueSelectionSetting (42.91s)
--- PASS: TestAccLexV2ModelsSlotType_disappears (43.63s)
--- PASS: TestAccLexV2ModelsSlotType_values (43.84s)
--- PASS: TestAccLexV2ModelsSlotType_basic (45.66s)
PASS
ok github.com/hashicorp/terraform-provider-aws/internal/service/lexv2models 51.940s
This functionality has been released in v5.68.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. |
Description
Add tests for
composite_slot_type_setting
as well as various fixes for naming errors and mix match.Previously the nested argument
sub_slots
was misnamed. There was a discrepancy between between the struct and schema - when the current name in the schema is used this error would occur:As such, though technically a break change, it is deemed acceptable within a minor release.
Relations
References
Output from Acceptance Testing