control-service: Introduce Executions in GraphQL Schema/API (#150)

* control-service: Introduce Executions in GraphQL Schema/API and update api.yaml to include executions option for GraphQL Endpoint

Why:
Job executions are important part of the data jobs details. They could be easily attached to the existing graphql schema/endpoint in order to extend the capabilities for the consumers.

What is done:
GraphQL schema is changed in order to provide future functionality for paging, sorting and filtering with the native graphql-way. Same mechanism with querying data jobs is applied, but this time as arguments in the executions fields

Testing:
Local run of tests and manual testing

Type of change:
Improvement of the current GraphQL Schema

Signed-off-by: Plamen Kostov <[email protected]>

projects/control-service/projects/model/apidefs/datajob-api/api.yaml

@@ -198,6 +198,40 @@ paths:
         }<br/>
         </pre><br/>
 
+        Data jobs execution could also be searched by providing arguments to the <b>execution</b> field.
+        Same as parent query arguments, the <b>pageNumber</b> and <b>pageSize</b> arguments are required! Page number should be a <b>number greater than 1</b>,
+        and pageSize <b>should be between 1 and 100 results</b> (per page). You can also <b>filter</b> using the similar object structure as the parent query,
+        but currently <b>filtering is not supported</b>, you can only provide field for sorting.
+        This query will search
+        <pre>
+        {<br/>
+          jobs(<br/>
+            pageNumber: 1,<br/>
+            pageSize: 25,<br/>
+          ) {<br/>
+            content {<br/>
+              jobName,<br/>
+              deployments {<br/>
+                id<br/>
+                executions(<br/>
+                  pageNumber: 1,<br/>
+                  pageSize: 5<br/>
+                  filter: [{<br/>
+                    property: "deployments.executions.startTime",<br/>
+                    sort: "DESC",<br/>
+                  }],<br/>
+                ) {<br/>
+                  id
+                  status
+                  startTime
+                  endTime
+                {</br>
+              }<br/>
+            }<br/>
+          }<br/>
+        }<br/>
+        </pre><br/>
+
         Full example of currently available for fetching fields. Note that if you combine searching and filtering, first
         it will apply filters and then within filtered jobs it will apply the search, vice versa is currently not supported:
         <pre>
@@ -240,6 +274,33 @@ paths:
                 enabled<br/>
                 jobVersion<br/>
                 mode<br/>
+                executions(<br/>
+                  pageNumber: 1,<br/>
+                  pageSize: 25<br/>
+                  filter: [{<br/>
+                    property: "deployments.executions.status",<br/>
+                    sort: "ASC",<br/>
+                  }],<br/>
+                ) {<br/>
+                  id<br/>
+                  type<br/>
+                  status<br/>
+                  message<br/>
+                  startTime<br/>
+                  endTime<br/>
+                  opId<br/>
+                  vkdVersion<br/>
+                  jobVersion<br/>
+                  jobSchedule<br/>
+                  resourcesCpuRequest<br/>
+                  resourcesCpuLimit</br>
+                  resourcesMemoryRequest</br>
+                  resourcesMemoryLimit</br>
+                  deployedDate</br>
+                  deployedBy</br>
+                  startedBy</br>
+                  logsUrl</br>
+                }<br/>
               }<br/>
             }<br/>
             totalPages<br/>

projects/control-service/projects/pipelines_control_service/src/main/resources/schema.graphqls

@@ -49,13 +49,23 @@ type DataJobResources {
 
 type DataJobExecution {
     id: String
+    type: DataJobExecutionType
     jobName: String
     status: DataJobExecutionStatus
     startTime: String
     endTime: String
     startedBy: String
     message: String
     opId: String
+    vkdVersion: String
+    jobVersion: String
+    jobSchedule: String
+    resourcesCpuRequest: Float
+    resourcesCpuLimit: Float
+    resourcesMemoryRequest: Int
+    resourcesMemoryLimit: Int
+    deployedDate: String
+    deployedBy: String
     logsUrl: String
 }
 
@@ -70,7 +80,7 @@ type DataJobDeployment {
     resources: DataJobResources
     schedule: DataJobSchedule
     vdkVersion: String
-    executions: [DataJobExecution]
+    executions(pageNumber: Int, pageSize: Int, filter: [Predicate]): [DataJobExecution]
     status: DataJobDeploymentStatus
 }
 
@@ -104,3 +114,8 @@ enum DataJobExecutionStatus {
     CANCELLED
     SKIPPED
 }
+
+enum DataJobExecutionType {
+    MANUAL
+    SCHEDULED
+}