refactor build system for deployment persistence #2

New Issue

pedro · 2024-02-06T10:14:53Z

pedro commented

2024-02-06 10:14:53 +00:00

first for idhub ( with 24739e3983 )
allow global override of persistence for all containers (for example, given the need from 2023-02-16 where we need an update without data migration)
second, other containers

1. [X] first for idhub ( with https://gitea.pangea.org/trustchain-oc1-orchestral/docker/commit/24739e3983b4ff27afaa4a9b4e7331190945947e ) 1. [x] allow global override of persistence for all containers (for example, given the need from 2023-02-16 where we need an update without data migration) 1. [x] second, other containers

pedro added this to the devOps and experimentation project 2024-02-06 10:15:02 +00:00

pedro referenced this issue from a commit

2024-02-06 13:30:46 +00:00

add persistence flag, which by default is yes

pedro referenced this issue from a commit

2024-02-06 13:51:40 +00:00

bugfix persistent idhubs were not updating code

pedro commented

2024-03-18 20:46:18 +00:00

now by default does persistence (default action is non harm action)

but test instances override with persistence=n, it is easy to run one shot without persistence in, for example, a pilot, persistence=n ./build__pilot-setem.sh

now by default does persistence (default action is non harm action) but test instances override with `persistence=n`, it is easy to run one shot without persistence in, for example, a pilot, `persistence=n ./build__pilot-setem.sh`

pedro closed this issue

2024-03-18 20:46:18 +00:00

This repo is archived. You cannot comment on issues.