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

Warn when using SENSIBLE_DEFAULTS #1420

Merged
merged 1 commit into from
Feb 20, 2024
Merged

Conversation

schneems
Copy link
Contributor

This feature provided a default WEB_CONCURRENCY value when SENSIBLE_DEFAULTS environment variable was set. This feature was experimental and never stabilized. It's not documented on devcenter and should not be relied on.

There are cascading complications in setting a default WEB_CONCURRENCY value:

  • A static default is difficult to determine without more information from runtime.
  • Multiple build packs have conflicting defaults for setting WEB_CONCURRENCY. For example, if an app is deploying with the Ruby buildpack and then they add the python buildpack after it, the WEB_CONCURRENCY defaults from python would be applied instead of Ruby.
  • Changes in WEB_CONCURRENCY in the buildpack are not picked up by apps unless they deploy.

@schneems schneems requested a review from a team as a code owner February 20, 2024 16:27
@schneems schneems force-pushed the schneems/warn-sensible-defaults branch from 5f3e320 to 5dc3c27 Compare February 20, 2024 16:29
This feature provided a default WEB_CONCURRENCY value when SENSIBLE_DEFAULTS environment variable was set. This feature was experimental and never stabilized. It's not documented on devcenter and should not be relied on.

There are cascading complications in setting a default WEB_CONCURRENCY value:

- A static default is difficult to determine without more information from runtime. 
- Multiple build packs have conflicting defaults for setting WEB_CONCURRENCY. For example, if an app is deploying with the Ruby buildpack and then they add the python buildpack after it, the WEB_CONCURRENCY defaults from python would be applied instead of Ruby.
- Changes in WEB_CONCURRENCY in the buildpack are not picked up by apps unless they deploy.
@schneems schneems force-pushed the schneems/warn-sensible-defaults branch from 5dc3c27 to d08bc5f Compare February 20, 2024 16:30
@schneems schneems merged commit a3fc8c5 into main Feb 20, 2024
3 checks passed
@schneems schneems deleted the schneems/warn-sensible-defaults branch February 20, 2024 16:44
This was referenced Feb 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants