r/servicecatalog_tag_option: New resource

[YakDriver]

Community Note

• Please vote on this pull request by adding a 👍 reaction to the original pull request comment to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for pull request followers and do not help prioritize the request

Relates #15369
Relates #18074
Relates #19122

Output from acceptance testing (us-west-2):

--- PASS: TestAccAWSServiceCatalogTagOption_disappears (11.33s)
--- PASS: TestAccAWSServiceCatalogTagOption_notActive (13.42s)
--- PASS: TestAccAWSServiceCatalogTagOption_basic (14.49s)
--- PASS: TestAccAWSServiceCatalogTagOption_update (47.60s)

Output from acceptance testing (GovCloud):

--- PASS: TestAccAWSServiceCatalogTagOption_disappears (14.15s)
--- PASS: TestAccAWSServiceCatalogTagOption_notActive (16.09s)
--- PASS: TestAccAWSServiceCatalogTagOption_basic (18.25s)
--- PASS: TestAccAWSServiceCatalogTagOption_update (60.28s)

Note: I'm not sure an AWS Organizations tests can ever run in GovCloud. GovCloud accounts are always tied to an existing commercial account so may not have the capacity of being a "payer" account.

[ewbankkit]

LGTM 🚀.

Commercial

% make testacc TEST=./aws TESTARGS='-run=TestAccAWSServiceCatalogTagOption_'
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./aws -v -count 1 -parallel 20 -run=TestAccAWSServiceCatalogTagOption_ -timeout 180m
=== RUN   TestAccAWSServiceCatalogTagOption_basic
=== PAUSE TestAccAWSServiceCatalogTagOption_basic
=== RUN   TestAccAWSServiceCatalogTagOption_disappears
=== PAUSE TestAccAWSServiceCatalogTagOption_disappears
=== RUN   TestAccAWSServiceCatalogTagOption_update
=== PAUSE TestAccAWSServiceCatalogTagOption_update
=== RUN   TestAccAWSServiceCatalogTagOption_notActive
=== PAUSE TestAccAWSServiceCatalogTagOption_notActive
=== CONT  TestAccAWSServiceCatalogTagOption_basic
=== CONT  TestAccAWSServiceCatalogTagOption_notActive
=== CONT  TestAccAWSServiceCatalogTagOption_update
=== CONT  TestAccAWSServiceCatalogTagOption_disappears
--- PASS: TestAccAWSServiceCatalogTagOption_disappears (11.62s)
--- PASS: TestAccAWSServiceCatalogTagOption_notActive (13.20s)
--- PASS: TestAccAWSServiceCatalogTagOption_basic (15.93s)
--- PASS: TestAccAWSServiceCatalogTagOption_update (47.09s)
PASS
ok  	github.com/terraform-providers/terraform-provider-aws/aws	50.096s

GovCloud

% make testacc TEST=./aws TESTARGS='-run=TestAccAWSServiceCatalogTagOption_'
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./aws -v -count 1 -parallel 20 -run=TestAccAWSServiceCatalogTagOption_ -timeout 180m
=== RUN   TestAccAWSServiceCatalogTagOption_basic
=== PAUSE TestAccAWSServiceCatalogTagOption_basic
=== RUN   TestAccAWSServiceCatalogTagOption_disappears
=== PAUSE TestAccAWSServiceCatalogTagOption_disappears
=== RUN   TestAccAWSServiceCatalogTagOption_update
=== PAUSE TestAccAWSServiceCatalogTagOption_update
=== RUN   TestAccAWSServiceCatalogTagOption_notActive
=== PAUSE TestAccAWSServiceCatalogTagOption_notActive
=== CONT  TestAccAWSServiceCatalogTagOption_basic
=== CONT  TestAccAWSServiceCatalogTagOption_notActive
=== CONT  TestAccAWSServiceCatalogTagOption_update
=== CONT  TestAccAWSServiceCatalogTagOption_disappears
--- PASS: TestAccAWSServiceCatalogTagOption_disappears (13.84s)
--- PASS: TestAccAWSServiceCatalogTagOption_notActive (15.82s)
--- PASS: TestAccAWSServiceCatalogTagOption_basic (22.73s)
--- PASS: TestAccAWSServiceCatalogTagOption_update (63.14s)
PASS
ok  	github.com/terraform-providers/terraform-provider-aws/aws	66.314s

[ghost]

This has been released in version 3.40.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 for triage. Thanks!

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