Use Jinja for workflow generation

[antalszava]

Context

The gen_workflow file contains code for generating Orquestra workflows that are then submitted to Orquestra locally. The sample workflow template for computing expectation values is stored at the moment as a dictionary. A YAML file is then created using this Python dictionary.

As the possible workflows to be generated by the plugin become more complex, it can be worth considering alternatives to storing workflow templates and steps as Python dictionaries internally.

One approach that could help maintainability and readability would be to turn to use Jinja for generating workflows.

[josh146]

@antalszava it might also be worth keeping an eye on GitHub actions to see if they support this feature without jinja.

In the plugin-test-matrix repo I used jinja as a 'cheat' to help re-use the same steps across numerous workflows, but it would be nicer if GitHub actions supported this natively (I believe they are working on it)

[antalszava]

Oh right! The thing is that these workflows are the ones that are generated locally by users and then used to submit workflows to Orquestra (edited the original description a bit). Was that that you had in mind? (Maybe misunderstanding how GitHub actions could be useful).

Jinja mostly came up as a templating solution that could help create workflow files locally before submitting to Orquestra.

[josh146]

Oops! My mistake, I thought you meant GitHub action workflows 🤦

[antalszava]

Oh no, the description was misleading, edited! 🙂