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.

Sign up for GitHub

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

Jump to bottom

Priority-Ordered Aspect Invocation #648

Closed
11 tasks done
sumupitchayan opened this issue Nov 5, 2024 · 0 comments
Closed
11 tasks done

Priority-Ordered Aspect Invocation #648

sumupitchayan opened this issue Nov 5, 2024 · 0 comments
Assignees
@sumupitchayan
Labels
status/done Implementation complete

Comments

@sumupitchayan
Copy link
Contributor

sumupitchayan commented Nov 5, 2024 •
edited
Loading

Description

Providing a priority-based system for invoking aspects on a construct tree. Each aspect can specify a priority level, and the aspect invocation algorithm will ensure that higher priority aspects are applied before lower priority ones, across the entire construct tree.

Roles

Role User
Proposed by @sumupitchayan
Author(s) @sumupitchayan
API Bar Raiser @rix0rrr @mrgrain
Stakeholders @alias, @alias, @alias

See RFC Process for details

Workflow

  • Tracking issue created (label: status/proposed)
  • API bar raiser assigned (ping us at #aws-cdk-rfcs if needed)
  • Kick off meeting
  • RFC pull request submitted (label: status/review)
  • Community reach out (via Slack and/or Twitter)
  • API signed-off (label status/api-approved applied to pull request)
  • Final comments period (label: status/final-comments-period)
  • Approved and merged (label: status/approved)
  • Execution plan submitted (label: status/planning)
  • Plan approved and merged (label: status/implementing)
  • Implementation complete (label: status/done)

Author is responsible to progress the RFC according to this checklist, and
apply the relevant labels to this issue so that the RFC table in README gets
updated.
@sumupitchayan sumupitchayan added the status/proposed Newly proposed RFC label Nov 5, 2024
@sumupitchayan sumupitchayan mentioned this issue Nov 7, 2024
Merged
@mrgrain mrgrain added status/review Proposal pending review/revision and removed status/proposed Newly proposed RFC labels Nov 12, 2024
sumupitchayan added a commit that referenced this issue Nov 29, 2024
@sumupitchayan @jiayiwang7
RFC648: Priority-Ordered Aspect Invocation (#651)
de610de 
This is a request for comments about Priority-Ordered Aspect Invocation.
See #648 for
additional details. 

APIs are signed off by @{BAR_RAISER}.

---

_By submitting this pull request, I confirm that my contribution is made
under
the terms of the Apache-2.0 license_

---------

Signed-off-by: Sumu <sumughan@amazon.com>
Co-authored-by: Joey Wang <jiayi.j.wang@gmail.com>
@sumupitchayan sumupitchayan added status/done Implementation complete and removed status/review Proposal pending review/revision labels Dec 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sumupitchayan sumupitchayan

Labels
status/done Implementation complete
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mrgrain @sumupitchayan