external dependency definition file

[JakeDEvans]

Summary

Please consolidate all external dependencies such as docker images (like alpine, busybox, postgres, zookeeper, kafka, clickhouse, nginx, exim) and package distributions (like buster debian) in one place so that this project can be easily installed and maintained behind highly firewalled and internet disconnect systems where package distribution systems like artifactory may be used.

Motivation

More clearly define external dependencies to make maintaining necessary internal changes manageable.

[chadwhitacre]

Seems reasonable. So we would pull all images from a single repository, which would be one that we (Sentry) control by default, but would be easy for you to override to point to your artifactory? Something like that?

[JakeDEvans]

Yes! not having to build locally would be preferred, if you can publish all images to a publicly accessible docker registry then it would be easy to override the images with those paths.

[chadwhitacre]

Makes sense. Marking as an enhancement, will see what kind of additional demand we get and if/when we can prioritize internally or see an external PR. 😁

Thanks for the suggestion and for using Sentry! :D

[BYK]

@chadwhitacre I guess we can build the cron images periodically ourselves?

[chadwhitacre]

Sorry ... what are the cron images?

[JakeDEvans]

Sorry ... what are the cron images?

https://github.com/getsentry/onpremise/blob/master/cron/Dockerfile

[chadwhitacre]

Gotcha, seeing it now for snuba and symbolicator cleanups (and I remember considering it for refreshing geoip data but deciding on install-time instead). I guess it'd be not just the cron images we'd have to build periodically but also everything that uses &sentry_defaults, no?

Why do we currently build on install vs. build-once? It has to do with configuration, I think?

[BYK]

Why do we currently build on install vs. build-once? It has to do with configuration, I think?

Not really the configuration at the moment. We had this for Sentry image where we embedded the config files into the locally-built image but we no longer do that. I don't see any good reason to build these images at install time except for the CI and storage costs we'd be paying for building and maintaining these images ourselves.

[chadwhitacre]

CI and storage costs we'd be paying for building and maintaining these images ourselves.

CI we probably end up doing anyway somewhere along the line, and Docker Hub is free for public images.

[github-actions[bot]]

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Accepted, I will leave it alone ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀