Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: ensure aspects run for Pipeline stages #94

Merged
merged 1 commit into from
Jul 15, 2022
Merged

Conversation

agdimech
Copy link
Contributor

@agdimech agdimech commented Jul 15, 2022

This PR fixes the below CDK issues by propagating all Aspects applied at the root level (App) to stages when they are added to the pipeline.

aws/aws-cdk#20468
aws/aws-cdk#17805

@nx-cloud
Copy link

nx-cloud bot commented Jul 15, 2022

☁️ Nx Cloud Report

We didn't find any information for the current pull request with the commit db2791d.
You might need to set the 'NX_BRANCH' environment variable in your CI pipeline.

Check the Nx Cloud Github Integration documentation for more information.


Sent with 💌 from NxCloud.

@agdimech agdimech merged commit 35082e0 into mainline Jul 15, 2022
@agdimech agdimech deleted the fix/stage_nag branch July 15, 2022 03:05
diranged added a commit to Nextdoor/cdk-pipelines-github that referenced this pull request Mar 24, 2024
The AWS CDK docs clearly state that `Aspects` do not cross `Stage`
boundaries ... which is an unexpected behavior. Its so unexpected that
Amazon's own `aws-pdk` project [implemented this
patch](aws/aws-pdk#94) to work around the issue.

Most of our projects use the `GItHubWorkflow` pipeline - so fixing it
here is a natural way to implement the behavior we _expect_ to see.

Ref: aws/aws-cdk#20468,
https://github.com/aws/aws-pdk/pull/94/files

Co-authored-by: Matt Wise <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant