i changed the pulumi name of an NS record which le...
# azure
b
i changed the pulumi name of an NS record which led to the expected preview of create / delete - but it did the create first which succeeded despite there being a clash, then it deleted "the old one" which left the DNS without the NS record at all - yet the stack had still had the resource in it so a second 'pulumi up' didnt fix it. a 'pulumi refresh' noticed it was missing and then i could recreate it. is it worth filing an issue for? is it likely to be fixable?