Single execution cleanup will not remove pods while task cleanup does

[chringwer]

When hitting the cleanup option under "Tasks" the corresponding REST call has both REMOVE_DATA and CLEANUP set in the action parameter:

spring-cloud-dataflow-ui/ui/src/app/shared/api/task.service.ts

Lines 123 to 135 in 46a218d

	taskExecutionsClean(task: Task, completed: boolean): Observable<any> {
	const headers = HttpUtils.getDefaultHttpHeaders();
	const paramCompleted = completed ? '&completed=true' : '';
	const paramTask = task ? `&name=${task.name}` : '';
	return this.httpClient
	.delete<any>(`/tasks/executions?action=CLEANUP,REMOVE_DATA${paramCompleted}${paramTask}`, {
	headers,
	observe: 'response'
	})
	.pipe(
	catchError(ErrorUtils.catchError)
	);
	}

When triggering the cleanup from the "Task Executions" panel only REMOVE_DATA is set and hence the kubernetes pods are left untouched.

spring-cloud-dataflow-ui/ui/src/app/shared/api/task.service.ts

Lines 107 to 117 in 46a218d

	executionClean(taskExecution: TaskExecution): Observable<any> {
	const headers = HttpUtils.getDefaultHttpHeaders();
	return this.httpClient
	.delete<any>(`/tasks/executions/${taskExecution.executionId}?action=REMOVE_DATA`, {
	headers,
	observe: 'response'
	})
	.pipe(
	catchError(ErrorUtils.catchError)
	);
	}

Is this intentional behaviour? I guess, it should be consistent at least or otherwise reflected in the label somehow so that the user is aware of those options actually behaving differently.