chore(enum-updater): exclude CUSTOM_INSTANCE_TYPE from codebuild ComputeType enum

[paulhcsun]

Reason for this change

CUSTOM_INSTANCE_TYPE value cannot be supported without additional logic. See https://docs.aws.amazon.com/codebuild/latest/userguide/build-env-ref-compute-types.html

• For the AWS CLI, run the create-fleet or update-fleet command, specifying the value of computeType to CUSTOM_INSTANCE_TYPE and the ComputeConfiguration instanceType to the specified instance type. For more information, see create-fleet or update-fleet.

• For the AWS SDKs, call the equivalent of the CreateFleet or UpdateFleet operation for your target programming language, specifying the value of computeType to CUSTOM_INSTANCE_TYPE and the ComputeConfiguration instanceType to the specified instance type. For more information, see the AWS SDKs and tools reference.

Description of changes

Exclude CUSTOM_INSTANCE_TYPE from codebuild ComputeType enum

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
• Commit ID: 028172e
• Result: SUCCEEDED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.