@aws-cdk/aws-cloud9-alpha: Missing owner- property

[jolo-dev]

Describe the bug

The @aws-cdk/aws-cloud9-alpha is missing the owner- property but the Cloudformation has it.

https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-cloud9-environmentec2.html#cfn-cloud9-environmentec2-ownerarn

Expected Behavior

Can add owner- property.

Current Behavior

owner is missing

Reproduction Steps

import * as cloud9 from '@aws-cdk/aws-cloud9-alpha';

const c9env = new cloud9.Ec2Environment(this, 'Cloud9Env', {
      vpc,
      imageId: cloud9.ImageId.AMAZON_LINUX_2,
      instanceType: new ec2.InstanceType('t3.large'),
      clonedRepositories: [
        cloud9.CloneRepository.fromCodeCommit(repo, '/src'),
      ],
     owner: 'arn::*' // error
 });

Possible Solution

Add all the Props from CfnEnvironmentEce the cloud9.Ec2Environment.

https:/aws/aws-cdk/blob/main/packages/%40aws-cdk/aws-cloud9/lib/environment.ts#L182

Additional Information/Context

No response

CDK CLI Version

2.45.0

Framework Version

No response

Node.js Version

16.13.1

OS

MacOS

Language

Typescript

Language Version

4.8.4

Other information

No response

[corymhall]

Yes, we should support that property.

This issue has been classified as p2. That means a workaround is available or it is deemed a nice-to-have feature. Given the amount of work there is to do and the relative priority of this issue, the CDK team is unlikely to address it. That does not mean the issue will never be fixed! If someone from the community submits a PR to fix this issue, and the PR is small and straightforward enough, and meets the quality bars to be reviewed and merged with little effort we will accept that PR. PRs that do not build or need complex or multiple rounds of reviews are unlikely to be merged and will be closed to keep our backlog manageable.

In the mean time, remember that you can always use the escape hatch (https://docs.aws.amazon.com/cdk/v2/guide/cfn_layer.html) mechanism to have fine control over the CloudFormation output you want. We will keep the issue open for discoverability, to collect upvotes, and to facilitate discussion around this topic.

We use +1s on this issue to help prioritize our work, and are happy to re-evaluate the prioritization of this issue based on community feedback. You can reach out to the cdk.dev community on Slack (https://cdk.dev/) to solicit support for reprioritization.

[jolo-dev]

Hey @corymhall,
Thanks for your message.
I am happy to pick up this issue and will contribute to it.

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