Ole Lensmar

@zdila in this specific case you could perhaps model your api as follows: PUT /v1/security/credentials/password -> changes the password (body contains new password) DELETE /v1/security/credentials/password -> resets the password POST...

nice! - how does this relate to https://github.com/kubeshop/testkube/issues/1277 ? would 1277 be an extension to this feature?

good point @hosumihaidarius - 1277 is mainly to help (new) users to onboard Testkube using existing tests with default executors - for more advanced scenarios we would need to provide...

get artifacts perhaps!?

I was just thinking something in the line of the output tabs that are usually found at the bottom of IDEs 

``` [2] 15:54:49.598 › Ignoring document 1 in deployment due to 1 error(s) [2] 15:54:49.665 › Ignoring document 1 in deployment due to 1 error(s) [2] 16:07:24.702 › SerializableStateInvariantMiddleware took...

nice catch @WitoDelnat 💪

Update: I tried creating a production build and the terminal works fine with the installed version of Monokle..!? Could it be something with my local environment!?

I've tried upgrading to electron 20.0.X in line with this fix - https://github.com/electron/electron/pull/35160 - but that results in errors when running a clean `npm install`: ``` • rebuilding native dependencies...

hm.. name/kind/namespace don't really apply to kustomizations or helm charts since these aren't really resources/deployable artifacts... my use-case was that I had a project with a lot of kustomize examples...