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

Document that this buildpack is only for Heroku Redis 5 and older #40

Merged
merged 1 commit into from
Jan 4, 2022

Conversation

edmorley
Copy link
Member

Since with Heroku Redis 6 and newer, the built-in TLS support should be used instead:
https://devcenter.heroku.com/articles/securing-heroku-redis

Since with Heroku Redis 6 and newer, the built-in TLS support should be used instead:
https://devcenter.heroku.com/articles/securing-heroku-redis
@edmorley
Copy link
Member Author

edmorley commented Jan 4, 2022

@beanieboi Could I have a review?

Also, I wonder if in a future PR, this buildpack should do a build-time check for a rediss:// (note the extra s) URL in REDIS_URL, and if found, abort the build with an error that the buildpack should not be used for Redis 6+? Or I suppose once Redis 5 and older are eventually no longer supported on the platform, we could just have the entire buildpack exit 1 during the build?

@beanieboi
Copy link
Member

sorry, this went under my radar. approved.

@edmorley edmorley merged commit f2bd5a6 into main Jan 4, 2022
@edmorley edmorley deleted the document-native-redis-tls branch January 4, 2022 11:57
edmorley added a commit to heroku/base-images that referenced this pull request Mar 21, 2024
Since:
- `heroku-buildpack-pgbouncer` hasn't used stunnel since 2018:
  heroku/heroku-buildpack-pgbouncer#104
- Redis 6 and newer support native TLS, making `heroku-buildpack-redis` redundant:
  heroku/heroku-buildpack-redis#40
  (The buildpack can be sunset now that old Redis instances have been shut down)
- If any other less common use-case needs stunnel, they can install it using APT.
- It reduces the run and build image sizes by 17 MB, and in a CNB world image size is a much bigger concern, so we need to be more selective about what packages we include.
- Once Heroku-24 GAs we can't remove packages (since it will break backwards compatibility given stack rebasing), however, we can add packages - so we should err on the side of trying out removing packages now.

Before:

```
-----> Size breakdown...
       heroku/heroku:24         441MB
       heroku/heroku:24-build   1.13GB
```

After:

```
-----> Size breakdown...
       heroku/heroku:24         424MB
       heroku/heroku:24-build   1.11GB
```

Towards #266.
GUS-W-15159536.
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