[TechDebt]: Add PreCheck step to CostExplorer acceptance tests

[jar-b]

Description

Several cost explorer acceptance tests can fail when run in a non-payer account.

=== NAME  TestAccCECostCategory_basic
    cost_category_test.go:30: Step 1/2 error: Error running apply: exit status 1

        Error: creating Cost Explorer Cost Category (tf-acc-test-7704009361025491562): operation error Cost Explorer: CreateCostCategoryDefinition, https response error StatusCode:
400, RequestID: 79b0c380-fc38-462d-87bb-7cdf3b6934d0, api error AccessDeniedException: Failed to create Cost Category: Linked account doesn't have access to cost category.

          with aws_ce_cost_category.test,
          on terraform_plugin_test.tf line 12, in resource "aws_ce_cost_category" "test":
          12: resource "aws_ce_cost_category" "test" {

A PreCheck step should be added to the affected tests which attempts to run the corresponding List API call and skips the test if an AccessDenied error is returned.

% aws ce list-cost-category-definitions

An error occurred (AccessDeniedException) when calling the ListCostCategoryDefinitions operation: Failed to list Cost Categories: Linked account doesn't have access to cost category.

References

No response

Would you like to implement a fix?

None

[github-actions]

Community Note

Voting for Prioritization

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

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[github-actions]

Warning

This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them.

Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.