rhythmic-finland-36256
02/10/2020, 9:20 AMpulumi up
runs (even during preview phase) with a project containing two `StackReference`s. It’s hanging on running read pulumi:pulumi:StackReference ajaegle/proj/stack
for ages and the super verbose log doesn’t list any more lines than the ones that were there since the beginning (the diff of some resources). I don’t expect that to be lossy internet connectivity as my machine is constantly using almost two cores for the pulumi process.mammoth-elephant-55302
02/10/2020, 10:06 AMpulumi up
in? I've noticed that if there are unrelated typescript files in the same directory then pulumi has some trouble and it slows down or stallsrhythmic-finland-36256
02/10/2020, 10:06 AMfiles
in tsconfig.json
didn’t help. My project contains several typescript files (all for pulumi), one typings folder with manually added type definitions for one library that didn’t support typings and the node_modules folder of course. That setup was the same for months.StackReference
was already resolved - I can see some content from the given stack (e.g. the exported kubeconfig) and some kubernetes resources using this resource that are diffed (and found to be same).ConfigFile
) I end up with a never halting process. The resources don’t use anything from the StackReference
as I’m just migrating to a self-contained pulumi project without stack references but I planned some soft migration with two clusters instead of tearing down one and creating a new one later.kubernetes.ConigFile
which has loads of resources. But I already did that with v0.11.0 before which was basically the same size.rapid-eye-32575
02/10/2020, 4:59 PMpulumi-kubernetes
package are at least v1.5.0
? And can you double-check the lock file if they all should be 1.5.0
? There has been a bug in 1.4.2 - 1.4.4
which resembles what you describe. See https://github.com/pulumi/pulumi-kubernetes/issues/963rhythmic-finland-36256
02/10/2020, 6:07 PM@pulumi/kubernetes
from 1.4.5
to 1.5.1
. 🎖️