|
|
#!/bin/bash
## When writing relation script, remember: ## - they should be idempotents ## - they can be launched while the dockers is already up ## - they are launched from the host ## - the target of the link is launched first, and get a chance to ``relation-set`` ## - both side of the scripts get to use ``relation-get``.
. lib/common
set -e
label=${SERVICE_NAME}-backup DST=$CONFIGSTORE/$TARGET_SERVICE_NAME/etc/cron/$label schedule=$(relation-get schedule)
if ! echo "$schedule" | egrep '^\s*(([0-9/,*-]+\s+){4,4}[0-9/,*-]+|@[a-z]+)\s*$' >/dev/null 2>&1; then err "Unrecognized schedule '$schedule'." exit 1 fi
exclude_dbs=$(relation-get exclude-dbs 2>/dev/null) || true exclude_dbs=$(echo "$exclude_dbs" | shyaml get-values 2>/dev/null | nspc) || true
## Warning: 'docker -v' will use HOST directory even if launched from ## 'cron' container. file_put "$DST" <<EOF COMPOSE_LAUNCHER_OPTS=$COMPOSE_LAUNCHER_OPTS
$schedule root lock $label -D -p 10 -c "\ docker run --rm \ -u 0 \ -e MONGO_HOST=${SERVICE_NAME} \ -e exclude_dbs=\"$exclude_dbs\" \ --network ${PROJECT_NAME}_default \ -v \"$HOST_CHARM_STORE/${CHARM_REL_PATH#${CHARM_STORE}/}/resources/bin/mongo-backup:/usr/sbin/mongo-backup\" \ -v \"$SERVICE_DATASTORE/var/backups/mongo:/var/backups/mongo\" \ --entrypoint mongo-backup \ \"$DOCKER_BASE_IMAGE\"" 2>&1 | ts '\%F \%T \%Z' >> /var/log/cron/${label}_script.log EOF chmod +x "$DST"
|