Oliver

Like discussed with @krucod3: In addition, we shall mark long running system tests and run them only in a nightly pipeline run. Because in #67 a stest might be added...

For better readability and single-point-of-change, I wanted to extract the conditions to check if certain steps shall be skipped into a environment variable and check the value of the env...

We can also think about changing the structure of workflows a little bit to group things within workflows together that belong together. For example: .github/workflows: ``` pr_validation.yml merge_validation.yml release.yml documentation.yml...

I have tested some different CI/CD setups and summarized up the following by putting it into a visualization:  Currently, our build job is using the rust-cache and does all...

@krucod3: I reduced the time now from ~6.5 minutes to ~ 4 min, see detailed explanation in the comment above. After removing the cache and better splitting the pipeline steps...

I added a user doc and a fix for the condition checking if long-runtime stests shall be skipped on pull request verification. I tested a final release build in my...

> **This PR is planned for the milestone 0.4. Do not merge the PR to the main yet.** According to @krucod3 we can merge this bug fix into v3.1.

> The following yaml show how the configs could look like: > > ```yaml > desiredState: > workload: > dashboard: > ... > configs: > c1: dashboard_configs > ports: ports...

After discussing the config reference complexity with @windsource and @krucod3, we decided to allow only one level of the `configs` field when referencing configurations in workload objects (like in the...

I decided to go with handlebars as template engine, because it is actively maintained, has an easy to use interface which fits well to our objects we work with and...