You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently Docker images for the task runner need to be manually built and pushed. Ideally it would be automatic (and across dev/staging/prod at the same time).
Affected product area (please put an X in all the brackets that apply)
[ ] Documentation
[ ] Data access
[x] Infrastructure
[ ] Loader pipeline
[ ] Other (please describe)
Additional context
This needs some figuring out, as the source of the images is 3 different docker repositories, and would be used differently. And it would be good to not rebuild but reuse images when possible, so we use the exact same version.
Eg.:
PR's build various images: sha + merge commit versions
Push to dev with those tags
Staging step tries to pull from the dev repository first, and if succeeds, retags and pushes to staging
After merge, the same thing happens (and retagging to prod) but across dev/staging/prod
Likely also needs some life-cycle rules to clean up old images and keep the space down.
This whole complexity could be avoided if using a single registry, but it would be either Github (which might be paid, and AWS would likely need a token to pull as images on Github don't seem to be publicly pullable), or Docker Hub (extra account), or something else (why else?).
In practice, that image doesn't change often (as is currently), so might not worth the added effort.
The text was updated successfully, but these errors were encountered:
Describe the feature request
Currently Docker images for the task runner need to be manually built and pushed. Ideally it would be automatic (and across dev/staging/prod at the same time).
Affected product area (please put an X in all the brackets that apply)
[ ] Documentation
[ ] Data access
[x] Infrastructure
[ ] Loader pipeline
[ ] Other (please describe)
Additional context
This needs some figuring out, as the source of the images is 3 different docker repositories, and would be used differently. And it would be good to not rebuild but reuse images when possible, so we use the exact same version.
Eg.:
dev
with those tagsdev
repository first, and if succeeds, retags and pushes tostaging
Likely also needs some life-cycle rules to clean up old images and keep the space down.
This whole complexity could be avoided if using a single registry, but it would be either Github (which might be paid, and AWS would likely need a token to pull as images on Github don't seem to be publicly pullable), or Docker Hub (extra account), or something else (why else?).
In practice, that image doesn't change often (as is currently), so might not worth the added effort.
The text was updated successfully, but these errors were encountered: