Clarification: Rename template into workflows and revisit what a workflow is today #452
Description
Ciao!
This is a long-standing topic we have. But I think it is time to make it happen.
Today we have templates and workflows.
A template is a reusable description of tasks and actions that we want to perform somewhere at some point. We are working around the concept of #438 and things like that.
A workflow represents the execution of a template at some point in time.
As far as they are designed today they are treated as resources, as long as hardware. But technically speaking a template yes, is a resource but a workflow is not.
You can create, update and delete a template. But a workflow can start, can't be edited, or removed.
What I am proposing is to rename template to workflow, mainly because template is really generic as a term, even workflow is but differently. it clearly set the expectation for something that can be executed multiple time.
What we know today as workflow can be renamed as execution, and it won't be a resource on its own, it will be strictly linked to a template (well... workflow 👍 I am already confusing myself)
Let me describe the interaction I have in my mind via Tink CLI
# equivalent of tink template create
tink workflow create
# equivalent of tink workflow create
tink workflow run <workflow_id> --data device_1=mac-address...
# list the execution of specific workflows
$ tink workflow list-executions <workflow_id>
# A lot of what is now under tink workflow will be moved under the new tink workflow