ninja
ninja
the first option 👍 and referring to the second one, I also found that to be buggy and if I reload the plugin many times inspections will stop refreshing at...
live-plugin eats the exceptions from inspection code, so that's something to be improved, took me a while to debug that. but that's not the problem here, because I already wrapped...
it's still not implemented. what year is it?
the diff was shown as just "~nodePool" ``` const cluster = new digitalocean.KubernetesCluster("cluster", { region: config.kubernetes.region, version: config.kubernetes.version, nodePool: { name: "default", size: digitalocean.DropletSlugs.DropletS2VCPU4GB, nodeCount: 2 }, }); ``` changing...
The same behaviour is when changing for example VPC on EKS cluster. What behavious should we use really? If pulumi is able to migrate the PVCs etc. maybe it's fine...
same bug after replace with EKS
I raised the issue upstream in Kotlin to get some attention to edge cases that generate class-based lambdas instead of the new `invokedynamic` based ones. With some luck, it will...