pvc/gen-api-migrations

#!/usr/bin/env bash

# Generate the database migration files

VERSION="$( head -1 debian/changelog | awk -F'[()-]' '{ print $2 }' )"

pushd $( git rev-parse --show-toplevel ) &>/dev/null
pushd api-daemon &>/dev/null
export PVC_CONFIG_FILE="./pvcapid.sample.yaml"
./pvcapid-manage_flask.py db migrate -m "PVC version ${VERSION}"
./pvcapid-manage_flask.py db upgrade
popd &>/dev/null
popd &>/dev/null
Use consistent shebangs in scripts 2023-10-17 10:35:38 -04:00			`#!/usr/bin/env bash`
Add DB migration update script 2020-02-15 23:23:09 -05:00
			`# Generate the database migration files`

			`VERSION="$( head -1 debian/changelog \| awk -F'[()-]' '{ print $2 }' )"`

Ensure all helper scripts pushd/popd Make sure all of these move to the root of the repository first, then return to where they were afterwards, using pushd/popd. This allows them to be executed from anywhere in the repo. 2021-11-06 03:16:02 -04:00			`pushd $( git rev-parse --show-toplevel ) &>/dev/null`
			`pushd api-daemon &>/dev/null`
Fix pvcapid config in migrations script 2020-03-15 17:33:27 -04:00			`export PVC_CONFIG_FILE="./pvcapid.sample.yaml"`
Update manage script 2023-11-16 23:12:53 -05:00			`./pvcapid-manage_flask.py db migrate -m "PVC version ${VERSION}"`
			`./pvcapid-manage_flask.py db upgrade`
Ensure all helper scripts pushd/popd Make sure all of these move to the root of the repository first, then return to where they were afterwards, using pushd/popd. This allows them to be executed from anywhere in the repo. 2021-11-06 03:16:02 -04:00			`popd &>/dev/null`
			`popd &>/dev/null`