Upload does not work, storage not configured about packages HOT 4 CLOSED

Sounds reasonable. However, would that mean, that Ditto would also support both use-cases: For a Ditto-Only deployment it would spawn its own MongoDB, while in the c2e package, the central instance would be used?

from packages.

As an alternative, we could utilize the MongoDB extension of hawkBit to store the uploaded artifacts there. I think this would be the cleaner solution. However, this would further increase the resource consumption of the stack (or is there already a MongoDB in place?).
What do you think?

from packages.

A MongoDB is already in place and started via the Ditto Helm chart.
If we want to use a shared one, we probably would need to add it as dependency to the "packages", disable the MongoDB dependency in the Ditto chart and configure Ditto to use the one from the package.
But that should work.

from packages.

As an alternative, we could utilize the MongoDB extension of hawkBit to store the uploaded artifacts there. I think this would be the cleaner solution. However, this would further increase the resource consumption of the stack (or is there already a MongoDB in place?).
What do you think?

I think adding both would be a good idea. Fixing the filesystem one for a simple Hawkbit only deployment. And MongoDB something more advanced. In the c2e package we could then activate MongoDB out of the box.

from packages.