Westly Wright 8906dd18cd gke project id not set before fetching cluster resources ... this issue cropped up after a large dependency upgrade and I believe it has to do with some underlying ember changes. Basically we'd hit a race condition where we'd click next before the observer has had a chance to update the project id. Found an additional issue where the observer on zone change would cause all the fetchs to fire again after the cluster has saved because we merge the results, I added checks to see if we'd saved as saving was already set false but we hadn't started destroying yet. rancher/rancher#29646		2020-10-22 08:55:12 -07:00
..
component.js	gke project id not set before fetching cluster resources	2020-10-22 08:55:12 -07:00
template.hbs	Amazon EKS V2	2020-07-22 16:09:14 -07:00