cleanup unused functions from management service about knix

[manuelstein]

Backwards compatibility
The management service constitutes our API, so removing functions (without a deprecation period) means we're breaking backward compatibility. That's okayish as we haven't reached out first major release, just pointing it out.

clearWorkflowLog IIUC is a placeholder that hasn't been implemented yet with Elasticsearch. Otherwise, I think we need a solution to manage log data in Elasticsearch. AS a side note, we should consider removing log data when removing a function.

[iakkus]

You mean, if somebody has written a piece of code that utilizes the Management service APIs (besides our code, like the SDK)? Sure, we could add the appropriate responses.

clearWorkflowLog and clearAllWorkflowLogs: we can modify them to indeed the delete the logs from Elasticsearch, but I think it might be better if we could automatically delete all logs after a certain amount of time (e.g., 30 days). For example,

• (https://blog.chesterwood.io/2019/06/how-to-delete-old-elasticsearch-logs.html)
• (https://www.elastic.co/guide/en/elasticsearch/client/curator/5.8/ex_delete_indices.html).

@paarijaat, what do you think?

[iakkus]

Implementation started on branch feature/cleanup_management.

[iakkus]

AS a side note, we should consider removing log data when removing a function.

I think perhaps removing the logs of a deleted workflow would make more sense.

[manuelstein]

Yes, of course, as we're not executing functions but workflows.

[iakkus]

New issue to track deletion of workflow logs: #25