(device-farm): Support for device farm constructs

[SamStephens]

Description

The AWS::DeviceFarm Cloudformation resources appear not to be exposed in the CDK at all.

This is a request for L1 constructs for those resources.

Use Case

To manage Device Farm resources via the CDK.

Proposed Solution

L1 Device Farm constructs.

Other information

No response

Acknowledge

• I may be able to implement this feature request
• This feature might incur a breaking change

[workeitel]

It looks like the problem is that the AWS CloudFormation resource specification is regional https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-resource-specification.html but CDK only imports from us-east-1: https://github.com/aws/aws-cdk/blob/main/packages/%40aws-cdk/cfnspec/build-tools/update.sh#L60

But AWS DeviceFarm service is only available in us-west-2 and therefore only part of the us-west-2 resource specification file.

[workeitel]

By comparing the different regional files it turns out only Device Farm resources are affected:

"AWS::DeviceFarm::DevicePool"
"AWS::DeviceFarm::InstanceProfile"
"AWS::DeviceFarm::NetworkProfile"
"AWS::DeviceFarm::Project"
"AWS::DeviceFarm::TestGridProject"
"AWS::DeviceFarm::VPCEConfiguration"

All other resources in any other region are also part of the us-east-1 resource specification.

[SamStephens]

Oh that's interesting. I guess this reflects an implicit assumption that products launch in us-east-1, and as such it's a framework-wide issue with the CDK. I've lodged #22565 to address this.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.