-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
42 refactor computation engine to be submodule for orchestrator for pipeline tests #43
42 refactor computation engine to be submodule for orchestrator for pipeline tests #43
Conversation
… into setup script for each component.
… docker compose file path as arguments. Also cleanup the scripts.
…-engine-to-be-submodule-for-orchestrator-for-pipeline-tests
…-engine-to-be-submodule-for-orchestrator-for-pipeline-tests
Tests will not succeed until we release and merge Project-OMOTES/orchestrator#36 into here as the database setup was moved. Right now, neither computation-engine setup nor the orchestrator (old version) is performing the db setup which causes the system to throw an error the first time a query to postgresql is performed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Much clearer with the database migration stuff moved and using as submodule instead of double setup components scripts in the orchestrator!
Just some minor comments.
…le-for-orchestrator-for-pipeline-tests
…nv vars are available during setup of the orchestrator database.
…date system tests.
Needs to be coordinated with Project-OMOTES/orchestrator#36