Arnaud M c79e903f49 Do not call setup_db from engine
Calling setup_db is creating the db structure if missing (because it's
calling models.Workbook.metadata.create_all after).

This is not what we want since we want the operator to manage the
creation of the db using mistral-db-manage like any other regular
openstack service.

I suspect that this call was mostly useful for tests.
This is a real issue in production because it create the DB structure
without using the correct alembic migration path (and thus,
alembic_version table is missing).

Change-Id: I51f4128dd023846a4406cd1b414a56d741035483
Signed-off-by: Arnaud M <arnaud.morin@gmail.com>
(cherry picked from commit 8be59adc38)
2025-09-23 19:44:32 +00:00
2025-01-10 00:37:34 +09:00
2024-01-25 01:29:48 +09:00
2025-09-23 19:44:32 +00:00
2024-10-06 12:29:06 +02:00
2025-03-17 10:38:18 +00:00
2018-05-30 14:46:25 -04:00
2013-12-30 13:11:49 +07:00
2023-11-14 20:51:51 +01:00
2019-10-23 09:26:22 +00:00
2025-02-10 10:17:39 +01:00
2017-03-03 10:17:44 +00:00
2025-01-10 00:37:34 +09:00

Team and repository tags

image

Mistral

Workflow Service integrated with OpenStack. This project aims to provide a mechanism to define tasks and workflows in a simple YAML-based language, manage and execute them in a distributed environment.

Project Resources

Description
Workflow Service for OpenStack.
Readme 52 MiB
Languages
Python 99%
Shell 0.9%