Replies: 3 comments 12 replies
-
Yep I think this makes a lot of sense. This is about a good a place to start for the mass renaming of things for clarity. |
Beta Was this translation helpful? Give feedback.
-
This is much clearer, although there may be some confusion between
|
Beta Was this translation helpful? Give feedback.
-
I really like that we're moving on from
# create a workflow
tink workflow create --file ubuntu20.04.yaml
# provision a machine
tink provision create --workflow <workflow_name or workflow_id> --hardware <hardware_name or hardware_id> |
Beta Was this translation helpful? Give feedback.
-
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
Beta Was this translation helpful? Give feedback.
All reactions