Patrick Titzler

> That said, I'd **love** to find a different (and optional) way of exposing these system-owned instances, but prior to that, a configurable for this makes sense. An approach similar...

Perhaps we should reevaluate whether this system-owned RTI metadata is even necessary. If I recall correctly, system RTIs were provided to provide a smother up-and-running experience. My thoughts: - For...

> We could also document how users could export/import the images they wish to retain. (Of course, we'd need the necessary import functionality in place, but I'm assuming this (removal...

 If one chooses (or leaves) the default selection, this is persisted in the `.pipeline` file: ``` "disallow_cached_output": "Use runtime environment default", ``` and ``` "properties": { ... "disallow_cached_output": "Use...

I edited a pipeline file when the VPE failed. The `.pipeline` file can no longer be opened due to  Console log: ``` 3935.4159b022aa6d82e44127.js?v=4159b022aa6d82e44127:2 TypeError: Cannot set properties of undefined...

Generic nodes: the `runtime image` property is now rendered as the last property in the list, even though it is the most important one: Pipeline properties:  Node properties: 

`Kubernetes pod annotations` widget: - Validation doesn't detect missing annotation value  As a result the invalid key/value combination is persisted in the `.pipeline` file and exported, producing an invalid...

`Environment variables` widget: - need to add placeholder values (`ENV_VAR`, `value`) that are consistent with other widgets  - if no key/value pair is enters a fatal error occurs during...

`data volumes` widget: - Validation error metadata is inconsistent across widgets. One would expect the same validation error to be raised if a constraint violation is detected. For example, assume...

`Kubernetes tolerations` widget: - `key` is not a required property. the previously implemented validation code should already have the complete logic built that verifies the constraints that need to be...