hoangthanh28
commented
7 months ago Currently, grate only supports a single environment per run, but you can create multiple runs, each per environment. My initial idea is to use the script (bash, powershell) to trigger multiple runs depending on the input variable. See the example below. My script
#!/bin/sh
# https://erikbra.github.io/grate/getting-started/
# https://erikbra.github.io/grate/configuration-options/
# https://github.com/erikbra/grate/tree/main/examples/k8s/multitenancy
# databasetype <mariadb | oracle | postgresql | sqlite | sqlserver
for i in $(echo ${Database__Env:-DEV} | tr "," "\n")
do
echo "Migrating to environment $i"
./grate --connectionstring "$Database__ConnectionString" \
--sqlfilesdirectory /db \
--environment ${i:-DEV} \
--databasetype ${Database__Type:-sqlserver} \
--schema ${Database__Schema:-grate} \
--silent \
--version ${VERSION:-1.0.0-beta1} \
--createdatabase ${Database__CreateDatabase:-true} \
--transaction ${Database__Transaction:-true} || exit 1
done
echo "Migration database completed."Grate Dockerfile build file ( I use docker, but you can choose which fit in your use case):
FROM ubuntu:jammy as grate-downloader
WORKDIR /app
ARG GRATE_VERSION=1.6.2
ADD https://github.com/erikbra/grate/releases/download/$GRATE_VERSION/grate-linux-musl-x64-self-contained-$GRATE_VERSION.zip /tmp/grate.zip
RUN apt update && apt install unzip -y
# extract grate to current folder /app
RUN unzip -d ./ /tmp/grate.zip
FROM alpine:3 as grate-migrator
WORKDIR /app
# COPY the sql script here or you can specify the mount volume at runtime
# COPY /sql /db
COPY --chmod=0755 --from=grate-downloader /app .
# migrate script
COPY --chmod=0755 migrate.sh .
# Add globalization support to the OS so .Net can use cultures
RUN apk add icu-libs
ENV DOTNET_SYSTEM_GLOBALIZATION_INVARIANT=false
ENTRYPOINT [ "./migrate.sh" ]Folder setup:
Run the migration script:
docker run -e Database__ConnectionString="connection_string_here" \
-e Database__CreateDatabase=true \
-v ./sql:/db \
-e Database__Env=DEV,TEST,CUSTOMER_A \
--network=host \
grate:latestGrate output:
JackNWeems
erikbra
Guess I get to be the one to request this. Being able to specify multiple environment per run as referenced in the missing RoundhousE features document would be a big help to us. We have a complex set of environment spread across our datacenter and Azure supporting multiple customers. Being able to specify multiple environments would let us use the environment names like tags and be able to run scripts against any environment matching that tag. We have a lot of environments that are very similar except for a couple of settings. It would be nice to be able to run a a script across all the UAT environments (we have 1 per customer) without having to name each UAT environment individually in the script. We have actually hit the windows file path limit a few times trying to get every environment named when using RoundhousE.