fix(core): removing the condition of non scaning stages children when invoking aspects #30612
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue # (if applicable)
Closes #17805 and #21341.
Reason for this change
The applying of aspects was stopping at the Stage level so not scanning the Constructs that the stage has a children.
Description of changes
I removed the following check as I don't think is required now and is blocking the applying of aspects into Constructs that are part of stages.
https://github.com/aws/aws-cdk/blob/8b495f9ec157c0b00674715f62b1bbcabf2096ac/packages/aws-cdk-lib/core/lib/private/synthesis.ts#L250C1-L250C35
Description of how you validated changes
I have done some local testing, but would be happy to add extra tests (probably integration is best) if required.
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license