Skip to content

Conversation

@aws-cdk-automation
Copy link
Collaborator

@aws-cdk-automation aws-cdk-automation commented Nov 26, 2025

See CHANGELOG

AWS CDK Team and others added 3 commits November 26, 2025 13:26
### Issue # (if applicable)

Closes #<issue number here>.

### Reason for this change

Remove the detail interface that was extending the
`cdk.AWSEventMetadataProps` as extending creates problems in python.

### Description of changes
Before 
```
    export interface ObjectCreatedDetail {
      readonly bucket?: BucketEvents.ObjectCreated.Bucket;
      ...otherfields
     }  
  
    export interface PatternProps extends BucketEvents.ObjectCreated.ObjectCreatedDetail {
      readonly eventMetadata?: cdk.AWSEventMetadataProps;
    }
```

After this change:
```
    export interface ObjectCreatedProps {
      readonly eventMetadata?: cdk.AWSEventMetadataProps;

      readonly bucket?: BucketEvents.ObjectCreated.Bucket;
      ...otherfields
    }
```

The Pattern functions have been updated to:
```
  public workSpacesAccessPattern(options?: WorkspaceEvents.WorkSpacesAccess.WorkSpacesAccessProps): events.EventPattern {
    return {
      source: ["aws.workspaces"],
      detailType: ["WorkSpaces Access"],
      detail: convertWorkSpacesAccessDetailToEventPattern(options, this.workspaceRef),
      version: options?.eventMetadata?.version,
      resources: options?.eventMetadata?.resources,
      region: options?.eventMetadata?.region
    };
  }
```
And the `convertWorkSpacesAccessDetailToEventPattern` functions ignore
the `eventMetadata` property.
### Describe any new or updated permissions being added

<!-- What new or updated IAM permissions are needed to support the
changes being introduced? -->


### Description of how you validated changes

<!-- Have you added any unit tests and/or integration tests? Did you
test by hand? -->
Added unit test to ensure that the metadata was still being passed to
the `EventPattern`
### Checklist
- [X] My code adheres to the [CONTRIBUTING
GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and
[DESIGN
GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md)

----

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

Co-authored-by: Leon Michalski <leonmk@amazon.de>
@aws-cdk-automation aws-cdk-automation requested a review from a team as a code owner November 26, 2025 20:14
@aws-cdk-automation aws-cdk-automation added auto-approve pr/no-squash This PR should be merged instead of squash-merging it labels Nov 26, 2025
@github-actions github-actions bot added the p2 label Nov 26, 2025
@aws-cdk-automation aws-cdk-automation requested a review from a team November 26, 2025 20:14
@mergify mergify bot added the contribution/core This is a PR that came from AWS. label Nov 26, 2025
@aws-cdk-automation aws-cdk-automation added the pr/needs-maintainer-review This PR needs a review from a Core Team Member label Nov 26, 2025
@mergify
Copy link
Contributor

mergify bot commented Nov 26, 2025

Merge Queue Status Beta

✅ The pull request has been merged

This pull request spent 6 seconds in the queue, with no time waiting for CI.
The checks were run in-place.

Required conditions to merge
  • #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • any of [🛡 GitHub branch protection]:
    • check-success = validate-pr
    • check-neutral = validate-pr
    • check-skipped = validate-pr
  • any of [🛡 GitHub branch protection]:
    • check-success = build
    • check-neutral = build
    • check-skipped = build

@mergify
Copy link
Contributor

mergify bot commented Nov 26, 2025

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

@mergify mergify bot merged commit 77f838d into main Nov 26, 2025
47 of 48 checks passed
@mergify mergify bot deleted the merge-back/2.230.0 branch November 26, 2025 20:45
@github-actions
Copy link
Contributor

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 26, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

auto-approve contribution/core This is a PR that came from AWS. p2 pr/needs-maintainer-review This PR needs a review from a Core Team Member pr/no-squash This PR should be merged instead of squash-merging it

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants