Oliver

Noting down some corner cases to be considered during implementation: - The state is updated to delete the whole `configs` field content. What shall be done with the workloads in...

@HorjuRares: I have created a fork in my private account, so that we can work both on the task. I thought about tasks that you can take over: - add...

I throw away the original idea of giving the ServerState its own type wrapping the CompleteState, which stores the workload objects unexpanded and expanded, because otherwise too many other fields...

After implementing the update logic for workloads with configs, I have tested the following cases: - update of `runtimeConfig` and some config item (e.g. access port) the workload uses +...

> @HorjuRares: I have created a fork in my private account, so that we can work both on the task. I thought about tasks that you can take over: >...

> > @HorjuRares: I have created a fork in my private account, so that we can work both on the task. I thought about tasks that you can take over:...

I had a look to the `ank apply` logic with @krucod3 and we came to the conclusion that `ank apply` behaves correctly for configs and updates. We improved the user...

I have covered the following State changes according to the table: # Configs cases ## Update state cases | User action | Expected Ankaios action | covered by | |------------------------------------------------------------------------------------------------|---------------------------------------------------------|-----------------|...

PR reviewed and merged. Summary written in the issue description. Issue can be closed.

> We can try a no-wrap functionality which cuts the line according to the size of the terminal. To enrich the "Pending(StartingFailed) No more retries." with more information we can...