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

Feature Flags #55

Closed
9 tasks done
eladb opened this issue Jan 1, 2020 · 0 comments
Closed
9 tasks done

Feature Flags #55

eladb opened this issue Jan 1, 2020 · 0 comments
Labels
effort/medium Reasonable effort required for implementation framework management/tracking status/done Implementation complete

Comments

@eladb
Copy link
Contributor

eladb commented Jan 1, 2020 •
edited
Loading

PR Champion
#56 @eladb

Description

Sometimes we want to introduce new breaking behavior because we believe this is
the correct default behavior for the CDK. The problem, of course, is that
breaking changes are only allowed in major versions and those are rare.

Feature flags are a pattern/mechanism which will allow us to introduce breaking behavior which is disabled by default (so existing projects will not be affected) but enabled automatically for new
projects created through cdk init.

Progress
@eladb eladb added the framework label Jan 1, 2020
@eladb eladb mentioned this issue Jan 1, 2020
Merged
eladb pushed a commit that referenced this issue Jan 3, 2020
RFC: #55 Feature Flags (#56)
e6776a1 
Design proposal for a pattern/mechanism that will allow us to introduce breaking capabilities which will only be applied to new projects created by "cdk init" and won't break old projects without explicit action from the user.

Transferred from aws/aws-cdk#5017
Tracking issue: #55
@eladb eladb changed the title Feature Flags RFC: Feature Flags Jan 3, 2020
@MrArnoldPalmer MrArnoldPalmer changed the title RFC: Feature Flags Feature Flags Jan 3, 2020
@MrArnoldPalmer MrArnoldPalmer added effort/medium Reasonable effort required for implementation status/approved Ready for implementation labels Jan 3, 2020
@eladb eladb self-assigned this Apr 7, 2020
@eladb eladb added status/done Implementation complete and removed status/approved Ready for implementation labels Apr 10, 2020
@eladb eladb removed their assignment Feb 25, 2021
@eladb eladb closed this as completed Feb 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
effort/medium Reasonable effort required for implementation framework management/tracking status/done Implementation complete
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@eladb @MrArnoldPalmer