Skip to content

Conversation

@Nvillaluenga
Copy link
Collaborator

Full workflow implementation.

Overall: This allow you to create custom workflows that are essentially a sequential set of steps that is going to be executed one after another, this steps allow you to do the almost the same as an user can in creative studio, create images, video, audio, etc. and allow users to have automation of repetitive tasks.

Backend:
There is 2 new big pieces in the back, worklfows and workflows_executor

  • Workflows: a backend that creates gcp workflows and the CRUD associated to this, to manage through the FE instead of using gcp workflows api directly, this allow us for better easier control and management.
  • Workflows_executor: Set of proxy endpoints that call the endpoints in the backend, this proxy is necesary because it helps abstract the logic between our endpoints and the logic of the workflows, this as already proven useful as when we changed to postgress some interfaces changed, and we could still rehuse the workflows already defined

Frontend:
This has many changes and is probably where the most complex logic resides, there are 3 new main pages, the workflow editor where you can create and edit workflwos, the workflows page where you can see a list of the workflows, and the workflows executions page where you can see past executions, the results and execute this workflows

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant