We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Now that the scheduler-v2-poc is done, we can proceed to the implementation of that in the api.
For that we need to create the Workflow.proto that will contain the resources needed to build a DAG Workflow that will run in Argo Workflow.
We should follow the following documentation from Argo: https://argoproj.github.io/argo-workflows/walk-through/the-structure-of-workflow-specs/
Resources that should be taken in account for creating the protos are:
We must also be able to specify metadata but this will mainly be for us in the backend to pinpoint to which users are the workflow tied to etc.
As part of this you should also create all the CRUD messages (DTO) like WorkflowCreationRequest, WorkflowDeletionRequest etc ...
WorkflowCreationRequest
WorkflowDeletionRequest
@viniciusdc please let me know if I am forgetting anything.
The text was updated successfully, but these errors were encountered:
Hi @Dr0p42 looks like you considered everything, I can't think of anything else that might be needed, but I am sure I will find it when they appear.
Sorry, something went wrong.
viniciusdc
Successfully merging a pull request may close this issue.
Now that the scheduler-v2-poc is done, we can proceed to the implementation of that in the api.
For that we need to create the Workflow.proto that will contain the resources needed to build a DAG Workflow that will run in Argo Workflow.
We should follow the following documentation from Argo: https://argoproj.github.io/argo-workflows/walk-through/the-structure-of-workflow-specs/
Resources that should be taken in account for creating the protos are:
We must also be able to specify metadata but this will mainly be for us in the backend to pinpoint to which users are the workflow tied to etc.
As part of this you should also create all the CRUD messages (DTO) like
WorkflowCreationRequest
,WorkflowDeletionRequest
etc ...@viniciusdc please let me know if I am forgetting anything.
The text was updated successfully, but these errors were encountered: