Background
When you load a hermes workflow with the CLI(hera-workflows add <path_to_workflow>) the metadata of the flow is saved in the DB. The workflow is always executed based on the metadata in the DB. This means if a change was made to the workflow file on disk it won't do anything until you sync this change with the db using hera-workflows sync <workflow_name>.
The sync command is a bit junky because it is also meant to show the user the changes made in the workflow parameters. If the nodes parameters(everything within the nodes field) are equal in both no change is made(even if fields besides nodes changed, e.g the solver field). If there are changes in the parameters then you would see them and the entire workflow will be synced(including the fields outside of nodes). In the case you want to sync everything no matter what then you use hera-workflows sync --forced <workflow_name>.
This is confusing and should probably be simplified, but it is how it works right now.
Bottom line:
There should be a sync button on hermes workflows in the UI that let the user sync. Its probably better to look at the changes between both jsons(disk and db) on the UI's end for clarity. Then the user will get the option to commit the changes from disk to the db.
If #565 is fixed then maybe we could use it in this case.
Background
When you load a hermes workflow with the CLI(
hera-workflows add <path_to_workflow>) the metadata of the flow is saved in the DB. The workflow is always executed based on the metadata in the DB. This means if a change was made to the workflow file on disk it won't do anything until you sync this change with the db usinghera-workflows sync <workflow_name>.The sync command is a bit junky because it is also meant to show the user the changes made in the workflow parameters. If the nodes parameters(everything within the
nodesfield) are equal in both no change is made(even if fields besidesnodeschanged, e.g thesolverfield). If there are changes in the parameters then you would see them and the entire workflow will be synced(including the fields outside ofnodes). In the case you want to sync everything no matter what then you usehera-workflows sync --forced <workflow_name>.This is confusing and should probably be simplified, but it is how it works right now.
Bottom line:
There should be a sync button on hermes workflows in the UI that let the user sync. Its probably better to look at the changes between both jsons(disk and db) on the UI's end for clarity. Then the user will get the option to commit the changes from disk to the db.
If #565 is fixed then maybe we could use it in this case.