-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unexpected diff with reserved ips #946
Comments
@kumavis thanks for your ticket and sorry you had issues. Given the resource was renamed it seems expected that the URN of the resource has changed too. What is anomalous about the diff? |
"floatingip" was renamed to "reservedip" internally at digitalocean, but refers to the same feature. (
|
@kumavis if you change the resource type for a resource that you have already created (i.e. I think this should work for your case. const reservedIp = new digitalocean.ReservedIp(`primary`, {
region,
}, {
aliases: [ { type: 'do:floatingip' } ],
}); |
i have not done this. i have not made any change. this diff is appear despite not making any change, thus "anomalous" diff.
thanks ill take a look |
@kumavis ah ok I misunderstood the issue. It looks like this is an issue with the upstream provider not yet supporting reserved ip in the Project resource. You could try the workaround they suggest or you could use the |
Describe what happened
"floatingip" was renamed "reservedip" at digitalocean. see the note at the top of this blog post
somewhere the old name is being used and shows up as an anomalous diff
Sample program
Log output
No response
Affected Resource(s)
No response
Output of
pulumi about
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: