IMO:
Because we do not have the versioning for all settings, the discard button
shall reset to last deployed state(in case if last deployed state exists,
otherwise the discard button should not be available).
Now the availability of discard button calculates according to state of
cluster, but
Folks,
Recently we were investigating an issue [1] when a user configured a cluster to
cause deployment to fail and then expected a discard button will allow to reset
changes made after that failure. As Julia mentioned in her comment on the bug,
basically what we’ve got is that users actually
