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

[CLI] change cluster creation cost savings mode default #14132

Merged
merged 4 commits into from
Aug 11, 2022

Conversation

nicolai86
Copy link
Contributor

@nicolai86 nicolai86 commented Aug 10, 2022

What does this PR do?

This PR changes the default for cluster creation:
instead of having customers opt-into cost savings mode, we'll ask them to opt-out of cost savings mode.

Based on internal discussions - see LAI2-10134

Does your PR introduce any breaking changes? If yes, please list them.

Before submitting

  • Was this discussed/approved via a GitHub issue? (not for typos and docs)
  • Did you read the contributor guideline, Pull Request section?
  • Did you make sure your PR does only one thing, instead of bundling different changes together?
  • Did you make sure to update the documentation with your changes? (if necessary)
  • Did you write any new necessary tests? (not for typos and docs)
  • Did you verify new and existing tests pass locally with your changes?
  • Did you list all the breaking changes introduced by this pull request?
  • Did you update the CHANGELOG? (not for typos, docs, test updates, or minor internal changes/refactors)

PR review

Anyone in the community is welcome to review the PR.
Before you start reviewing, make sure you have read the review guidelines. In short, see the following bullet-list:

  • Is this pull request ready for review? (if not, please submit in draft mode)
  • Check that all items from Before submitting are resolved
  • Make sure the title is self-explanatory and the description concisely explains the PR
  • Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?

Make sure you had fun coding 🙃

cc @Borda

@github-actions github-actions bot added the app (removed) Generic label for Lightning App package label Aug 10, 2022
@hhsecond
Copy link
Contributor

Do we have the "cluster" feature documented already?

@lantiga
Copy link
Collaborator

lantiga commented Aug 10, 2022

Wouldn't it make sense to turn it around and have an enable-performance flag instead?

@nicolai86
Copy link
Contributor Author

Wouldn't it make sense to turn it around and have an enable-performance flag instead?

I agree, avoiding the negation makes the flag more readable. let me change that.

@mergify mergify bot added the ready PRs ready to be merged label Aug 10, 2022
@nicolai86
Copy link
Contributor Author

nicolai86 commented Aug 10, 2022

Do we have the "cluster" feature documented already?

the documentation is in a pending PR, I'll leave a comment to adjust it according to this change. @hhsecond

@nicolai86 nicolai86 mentioned this pull request Aug 10, 2022
12 tasks
@mergify mergify bot requested a review from a team August 10, 2022 16:28
instead of having customers opt-into cost savings mode, we'll ask them to opt-out of cost savings mode.
--disable-cost-savings is less clear than --enable-performance
@nicolai86 nicolai86 force-pushed the nicolai86/cluster-creation-defaults branch from 1407e40 to 7715b1a Compare August 10, 2022 21:07
@nicolai86 nicolai86 added this to the app:0.6 milestone Aug 11, 2022
@nicolai86 nicolai86 merged commit 98ded45 into master Aug 11, 2022
@nicolai86 nicolai86 deleted the nicolai86/cluster-creation-defaults branch August 11, 2022 15:19
jessecambon pushed a commit to jessecambon/lightning that referenced this pull request Aug 16, 2022
…#14132)

* [CLI] change cluster creation cost savings mode default

instead of having customers opt-into cost savings mode, we'll ask them to opt-out of cost savings mode.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
app (removed) Generic label for Lightning App package ready PRs ready to be merged
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants