You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We don't have a pattern for disabling the save button if there are no changes. If something is invalid though it should be.
The service is very often not updated at all (backend?)
@andreas-kupries In #345 (comment) it looks like the fields changed in the epinio service kick off changes to restricted properties in associated kube resources. Is that correct, if so is the test case valid and do we need to document this kind of thing somewhere?
We don't have a pattern for disabling the save button if there are no changes. If something is invalid though it should be.
ok, thanks
The service is very often not updated at all (backend?)
...it looks like the fields changed in the epinio service kick off changes to restricted properties in associated kube resources. Is that correct, if so is the test case valid and do we need to document this kind of thing somewhere?
It is fine with "simpler" nginx bitnami service, report here.
The problem with mysql was likely a conflict between E internal values.extraDeploy keys in the mysql service definition and my custom settings (related to storage) - other values like password and port number doesn't collide and the Edit always works for them.
Edit side of #252
Dependent on now provided ability to edit service chart values - epinio/epinio#2522
The text was updated successfully, but these errors were encountered: