Joe McDonald
08/04/2021, 6:00 PMmutation {
create_flow_run(
input: {
flow_id: "f667e3f3-b5eb-4c52-8f90-36bc54633ac9",
parameters: "{\"file_id\": \"42556bd0-f495-11eb-a7a0-8c8590acd4d8\"}"
}
) {
id
}
}
Which gives this output. We are getting the same output from our code that runs against graphql endpoint to trigger a flow run and has been working fine for months on 0.14.15.
{
"errors": [
{
"message": "[{'extensions': {'path': '$.variableValues.insert_on_conflict.constraint', 'code': 'validation-failed'}, 'message': 'unexpected value \"ix_flow_run_idempotency_key_unique\" for enum: \\'flow_run_constraint\\''}]",
"locations": [
{
"line": 2,
"column": 3
}
],
"path": [
"create_flow_run"
],
"extensions": {
"code": "INTERNAL_SERVER_ERROR",
"exception": {
"message": "[{'extensions': {'path': '$.variableValues.insert_on_conflict.constraint', 'code': 'validation-failed'}, 'message': 'unexpected value \"ix_flow_run_idempotency_key_unique\" for enum: \\'flow_run_constraint\\''}]"
}
}
}
],
"data": {
"create_flow_run": null
}
}
PREFECT_SERVER_DB_CMD
env variable and changed command to /usr/local/bin/prefect-server database upgrade --yes
https://github.com/PrefectHQ/server/blob/master/helm/prefect-server/templates/graphql/deployment.yamldb-upgrade alembic upgrade postgres ix_flow_run_idempotency_key_unique
Kevin Kho
Marvin
08/04/2021, 8:39 PMKevin Kho
prefect server start
with docker-compose or using the helm chart.