Changelog (Breaking Changes)

List of backward incompatible changes that might affect your self-hosted Databand installation.

πŸ“˜

New service for statics in 0.44

A separate nginx-based service for serving static files was introduced in v0.44. New Docker image looks like this:

  • DOCKER_IMAGE_DBND_WEBAPP=registry.gitlab.com/databand/databand-deploy/dbnd-webapp:py36-v0.44.0

❗️

Backward incompatible change in 0.43

We have changed naming conventions for Docker images and switched to an "Image per Service" approach. The following Docker images now replace the obsolete all-in-one image:

  • DOCKER_IMAGE_DBND_WEBSERVER=registry.gitlab.com/databand/databand-deploy/dbnd-webserver:py36-v0.43.0
  • DOCKER_IMAGE_DBND_ALERT_DEFS_SYNCER=registry.gitlab.com/databand/databand-deploy/dbnd-alert-defs-syncer:py36-v0.43.0
  • DOCKER_IMAGE_DBND_ML_TRAINER=registry.gitlab.com/databand/databand-deploy/dbnd-ml-trainer:py36-v0.43.0
  • DOCKER_IMAGE_DBND_AIRFLOW_SYNC_MONITOR=registry.gitlab.com/databand/databand-deploy/dbnd-airflow-monitor:py36-v0.43.0
  • DOCKER_IMAGE_DBND_AIRFLOW_EXAMPLE=registry.gitlab.com/databand/databand-deploy/dbnd-airflow-example:py36-v0.43.0

All-in-one Docker images of the following type registry.gitlab.com/databand/databand-deploy:dbnd-v0.xx.xx won't be released starting with version 0.43.


What’s Next
Did this page help you?