you said earlier: “when I start a server it complains…” and then posted an error which can only come from the boundary database init
now, you’ve posted a set of OR’d commands which would attempt to migrate the db and if it fails, assume that the db hasn’t been initialized and attempt to init the db. But I don’t see the connection between these and the earlier “when I start a server…” that results in an init error.
Perhaps I’m don’t know enough about your deployment env.
I am trying to deploy into Kubernetes. With k8s you can specify an init-container that runs before the main process. I configured my deployment to run this command in the init-container boundary database migrate -config /boundary/config.hcl || boundary database init -config /boundary/config.hcl || sleep 300
Then the main process starts with this command boundary server -config /boundary/config.hcl
Both containers are sharing the volume with the config.hcl