Mario Loriedo
Mario Loriedo
/remove-lifecycle stale
@max-cx this issue is about updating the server properties so that we can resume publishing them in the doc. From a priority point of view though, I don't think this...
@max-cx cleaning up `che.properties` is not easy (this issue has been open for 1 year) and the benefits are not clear. So until we get a customer/user request for that...
@azatsarynnyy 👍 For confirmation: this is not about adding a file watcher mechanism and it's not about prompting the user when he edits the file right? And maybe, to avoid...
/remove-lifecycle stale
che-operator should watch for Secrets/ConfigMaps/PersistentVolumeClaims, with the following labels, in the Che namespace: ```yaml labels: app.kubernetes.io/part-of: che.eclipse.org app.kubernetes.io/component: workspaces-config ``` For example if, a ConfigMap like the following one is...
> @l0rd The side effect of syncing PVC is that we will have one extra PV created on the cluster. Is it ok for us? Yes, that's fine. That's something...
Removing those 2 tasks from this epic and closing it - [ ] #21753 - [ ] https://github.com/eclipse/che/issues/21291
/remove-lifecycle stale
Moving this issue to milestone 7.60.