This message was deleted.

When you select Details from the "Do you want to perform this update" prompt it should show you what inputs are different.

Thanks for the suggestions. The warnings seem to come from that a new IP is allocated to those resources for some reason. Will look into that a bit more when at home again. Another problem I found was when trying to import DNSRecords under a domain I get errors that says that "domain can't be an empty string" even when I refer to a domain that already exist in Digitalocean and declared as a variable in the TS code.

const tld = new digitalocean.Domain('<http://tld.com|tld.com>', {...}, {import: 'identifier'});
const sub = new digitalocean.DnsRecord('<http://sub.tld.com|sub.tld.com>', {
    domain = tld.name,
    ...
}, {import: 'identifier'});

The empty string thing is the same even when I hardcode the domain in the subdomain.

I think this is a nuance of https://github.com/pulumi/pulumi/pull/3327, which should be fixed in the next couple weeks. In the meantime, if you hardcode the domain in the

digitalocean.DnsRecord

resource I believe it will import fine and then you can revert to using the

tld.name

reference.