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

L2 ElastiCache support #456

Closed
10 of 11 tasks
dbartholomae opened this issue Sep 27, 2022 · 4 comments
Closed
10 of 11 tasks

L2 ElastiCache support #456

dbartholomae opened this issue Sep 27, 2022 · 4 comments
Labels
l2-request request for new L2 construct management/tracking

Comments

@dbartholomae
Copy link
Contributor

dbartholomae commented Sep 27, 2022

Description

Adding a first L2 construct for ElastiCache ReplicationGroups which will take care of SubnetGroups as well.

Roles

Role User
Proposed by @dbartholomae
Author(s) @dbartholomae
API Bar Raiser @corymhall
Stakeholders not yet decided

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.

@dbartholomae
Copy link
Contributor Author

Added @corymhall as API bar raiser

corymhall pushed a commit that referenced this issue Feb 27, 2023
This is a request for comments about an RFC to add L2 constructs to ElastiCache. See #456 for
additional details.

APIs will be signed off by @corymhall.
@dbartholomae
Copy link
Contributor Author

@corymhall
Sooo - if I understand correctly, the next step is an execution plan? Or can I just go at implementing parts and create a PR for the aws cdk repo?
We didn't actually add all the labels that are shown in the first comment in this thread in the check list, so if I need to add some of those, please let me know as well.

@corymhall corymhall added status/implementing RFC is being implemented and removed status/proposed Newly proposed RFC labels Apr 10, 2023
@corymhall
Copy link
Contributor

@dbartholomae we can move right into implementing.

@evgenyka evgenyka added l2-request request for new L2 construct bar-raiser/assigned labels Aug 10, 2023
@awsmjs
Copy link
Contributor

awsmjs commented Dec 15, 2023

Closing this ticket. We believe the functionality is beneficial, but does not intersect with the core framework and should be vended and maintained separately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
l2-request request for new L2 construct management/tracking
Projects
None yet
Development

No branches or pull requests

4 participants