-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Make images versions configurable #596
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
Make images versions configurable #596
Conversation
By default `SENTRY_VERSION=latest` in `.env`, but if I set it to `SENTRY_VERSION=b7d0b43` then install script fails, because there is no such image tag for `getsentry/snuba` and `getsentry/relay`, but `docker-compose.yml` contained `image: 'getsentry/snuba:$SENTRY_VERSION'` and `image: 'getsentry/relay:$SENTRY_VERSION'`. I propose to make configurable tags for snuba and relay images.
|
Reopening PR for Travis rebuild with new timeout settings. |
BYK
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot for the PR! I had something similar in mind but using SNUBA_IMAGE and RELAY_IMAGE similar to the one we already have: SENTRY_IMAGE.
Separating these would make our release process more complex and your PR would break it as it currently is.
Would you mind if I suggest you to use SENTRY_IMAGE for now and then create a PR of my own implementing the solution I mentioned? We'll need that for some tests in the near future.
|
I don't mind closing my PR. Thanks for sharing your future plans about implementing this feature. |
This change allows one to override any Sentry service image, mostly for testing purposes. It also removes the SENTRY_VERSION variable as docker-compose makes it very hard to cascade default values for these. Next step is to have integration tests in getsentry/snuba and getsentry/relay (and possibly for getsentry/symbolicator) for getsentry/onpremise using this PR. Also related: #596.
#602) This change allows one to override any Sentry service image, mostly for testing purposes. It also removes the SENTRY_VERSION variable as docker-compose makes it very hard to cascade default values for these. Next step is to have integration tests in getsentry/snuba and getsentry/relay (and possibly for getsentry/symbolicator) for getsentry/onpremise using this PR. Also related: #596.
#602) This change allows one to override any Sentry service image, mostly for testing purposes. It also removes the SENTRY_VERSION variable as docker-compose makes it very hard to cascade default values for these. Next step is to have integration tests in getsentry/snuba and getsentry/relay (and possibly for getsentry/symbolicator) for getsentry/onpremise using this PR. Also related: #596.
By default
SENTRY_VERSION=latestin.env, but if I set it toSENTRY_VERSION=b7d0b43then install script fails, because there is no such image tag forgetsentry/snubaandgetsentry/relay, butdocker-compose.ymlcontainedimage: 'getsentry/snuba:$SENTRY_VERSION'andimage: 'getsentry/relay:$SENTRY_VERSION'.I propose to make configurable tags for snuba and relay images.