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

AppConfig L2 Construct #426

Closed
1 of 11 tasks
yamatatsu opened this issue Apr 22, 2022 · 2 comments
Closed
1 of 11 tasks

AppConfig L2 Construct #426

yamatatsu opened this issue Apr 22, 2022 · 2 comments
Labels
management/tracking status/stale The RFC did not get any significant enough progress or tracking and has become stale.

Comments

@yamatatsu
Copy link

yamatatsu commented Apr 22, 2022 •
edited
Loading

Description

I would like to implement AppConfig L2 Construct. It has already got enough votes (see, aws/aws-cdk#6831). Also, I believe that CDK, which is more application-oriented than CFn, will be able to manage AppConfig well, which will create a variety of value.

Roles

Role User
Proposed by @yamatatsu
Author(s) @alias, @alias, @alias
API Bar Raiser @alias
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 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.
@neo01124
Copy link

neo01124 commented Apr 3, 2023

Is this L2 construct already merged? Wondering since this issue is completed but the feature request is open aws/aws-cdk#6831

@evgenyka
Copy link

No, it was not implemented, the RFC was abandoned.

@chenjane-dev chenjane-dev mentioned this issue Apr 20, 2023
Closed
11 tasks
@mrgrain mrgrain added status/stale The RFC did not get any significant enough progress or tracking and has become stale. and removed status/proposed Newly proposed RFC labels Nov 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
management/tracking status/stale The RFC did not get any significant enough progress or tracking and has become stale.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@neo01124 @mrgrain @evgenyka @yamatatsu