When checking for updates to the Metadata Service ...
# ask-metaflow
f
When checking for updates to the Metadata Service / UI Service, are there any specifics to look out for that call out when DB migrations are available via Github/Dockerhub? For the Metadata Service version, I look at the release version of https://github.com/Netflix/metaflow-service which aligns with Dockerhub. For the UI Service version, I look at the dockerfile, e.g.
ARG UI_VERSION="v1.2.5"
. These can be easily compared to the application/service versions under "quick links" in a deployed UI. For potential DB migrations (without first upgrading the deployment and pinging the service), I just take a look inside the
migration_service
subdirs. To put another way, I think what I'm looking for is when new releases are made to the metadata service repo, it's easy to see which services are affected so deployments can be updated accordingly: • Metadata Service • UI Service • [ ] Migration Service It's a minor nit, but thought I'd double check and make sure I'm not missing something obvious 🙂
1