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

Standardized context key for "cheap mode" #248

Closed
1 of 7 tasks
rix0rrr opened this issue Sep 7, 2020 · 1 comment
Closed
1 of 7 tasks

Standardized context key for "cheap mode" #248

rix0rrr opened this issue Sep 7, 2020 · 1 comment
Labels
management/tracking status/stale The RFC did not get any significant enough progress or tracking and has become stale.

Comments

@rix0rrr
Copy link
Contributor

rix0rrr commented Sep 7, 2020

PR Champion
#

Description

It would be good if we had a standardized context key for "cheap mode" deployments, which people could set on development mode stacks.

If set, the presence of the key would control:

  • Smaller default instance sizes
  • Lower default replication factors
  • Use default KMS key instead of custom one
  • VPS with only public subnets by default
  • ...etc...

The advantage of having a single well-established key for this would be semantics: the alternative is ad-hoc keys established on a per-module basis, for the same functionality.

Not all modules have to support it, but the ones that do should trigger off the same key.

Support for this key in various modules can be added piecemeal via PRs and can be community-contributed.

Progress

  • Tracking Issue Created
  • RFC PR Created
  • Core Team Member Assigned
  • Initial Approval / Final Comment Period
  • Ready For Implementation
    • implementation issue 1
  • Resolved
@mrgrain
Copy link
Contributor

mrgrain commented Oct 27, 2023

Marking this RFCs as stale since there has been little recent activity and it is not currently close to getting accepted as-is. We appreciate the effort that has gone into this proposal. Marking an RFCs as stale is not a one-way door. If you have made substantial changes to the proposal, please open a new issue/RFC. You might also consider raising a PR to aws/aws-cdk directly or self-publishing to Construct Hub.

@mrgrain mrgrain closed this as not planned Won't fix, can't repro, duplicate, stale Oct 27, 2023
@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 Oct 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
management/tracking status/stale The RFC did not get any significant enough progress or tracking and has become stale.
Projects
None yet
Development

No branches or pull requests

2 participants