Enhance Data for Deployments about kaoto-backend HOT 1 CLOSED

datetime can probably be returned, I need to check.

namespace is kind of dummy to return right now because it is included as a parameter on the query to return the list of deployments. But we can add it, just in case we extend it to support multiple namespaces.

Problematic data:

errors is kind of problematic because it means reading from the log of the camel-k operator (or whatever operator we use if we move beyond camel) and check what is happening. I will return an empty array for now, but not sure how to fill this. Even for a human reading the camel-k operator log it is sometimes not clear where is the error and to what deployment it refers to.

For the same reason, running may be difficult to map to something that is not a "Running" or "Stopped". Each type of CustomResource have a different set of statuses. The boolean simplifies the whole list. If we allow more statuses... what would they be? Do we mimic KameletBindings?

version is a concept we don't have right now. To return it we need first to define what version means for us.

cluster is also weird because clusters don't have a name. What should I return then?

number of steps is also an advanced feature that probably requires a bit more definition once we enter the EIP world. I can parse each CRD and try to get the number of steps, but is it not a bit overkill for just the list of deployments?

user that deployed it is something we also don't have.

from kaoto-backend.