This message was deleted.
# dotnets
sparse-intern-71089
02/06/2020, 10:56 AMThis message was deleted.
d
delightful-dawn-43855
02/06/2020, 10:59 AMI usually resolve the issue by doing a "pulumi refresh" before I do a "pulumi up", but that should be necessary? Right? And by the way, thanks for a good product!
t
tall-librarian-49374
02/06/2020, 11:04 AMI haven’t seen this before. What is the diff that pulumi reports?
tall-librarian-49374
02/06/2020, 11:07 AMI wonder if something fishy happens because you update the same args to use in two queues. Could you try creating two separate args objects?
tall-librarian-49374
02/06/2020, 11:09 AMFor example, make
DefaultQueueSettingd
delightful-dawn-43855
02/06/2020, 11:13 AMHow can I see exactly wish diff pulumi detectes? apart from ~name that it's stated in the output?
t
tall-librarian-49374
02/06/2020, 11:57 AMYou could select Details in the menu of
pulumi upd
delightful-dawn-43855
02/06/2020, 12:22 PMHihi.. I have seen that menu-choice more than a 100 times, never tried it 🙂 But I think you might be on to something, Pulumi seem to be intermixing the queues with eachother, in the case above the first queue is compared with the second in Azure and vice versa... will try a function instead of just replacing the name. Thanks!
t
tall-librarian-49374
02/06/2020, 12:26 PMThere’s a multi-threading story going on there, so the two queues’ parameters likely mingle. I’ll open an issue to investigate whether we can make it safer.
tall-librarian-49374
02/06/2020, 12:27 PMActually, if you want to open an issue in https://github.com/pulumi/pulumi/, that would be great :)
d
delightful-dawn-43855
02/06/2020, 12:32 PMBreaking out the creation of the queue to a function seems to work more stable. It's probably way better practice to do it like that...