DNS Record Not Updated #952
Labels
awaiting-feedback
Blocked on input from the author
kind/bug
Some behavior is incorrect or out of spec
needs-repro
Needs repro steps before it can be triaged or fixed
Milestone
Comments
IdoOzeri
added
kind/bug
|
It looks like there's been a deprecation warning added to the |
True, but why is it a warning? If it's deprecated effective-immediately and should not be used - then you should throw an error. |
|
Hi @IdoOzeri - we're sorry your encountering trouble here. I've run a basic Zone + Record example using => Looking at the zone on cloudflare console; the record exists: => pulumi up sends the same deprecation warning; upgrade runs successfully. Looking at the zone on cloudflare console, I do need to refresh the page, but the record has successfully been updated. If you do continue to see this behavior on your side, please send us a minimal runnable repro that shows this bug. |
guineveresaenger
added
needs-repro
|
@guineveresaenger I was able to reproduce this with this Python program: import pulumi
import pulumi_cloudflare as cloudflare
config = pulumi.Config()
zone = cloudflare.Zone("zd6105-zone",
zone = 'py-test-cloudflare-pulumi.com',
account_id = config.require_secret('accountId'),
)
# Add a record to the domain
example = cloudflare.Record("zd6105-record",
zone_id = zone.id,
name = "example",
value = "192.0.2.2",
type = "A",
ttl = 3600,
)and The change is not applied to the record. I even have Pulumi detecting that the change still needs to be applied at every --
|
|
Hi @ringods - I looked into this today and...I cannot reproduce this behavior with your example. A few notes, in case I'm doing something differently without realizing (I'm not fluent in Python anymore):
Pulumi output: -- pulumi about: The one thing that gives me pause here is that the zone is officially Pending on Cloudflare since there are a few missing steps to make this test program a "real" zone: https://developers.cloudflare.com/dns/zone-setups/reference/domain-status/#pending
The fact that zones can be in Pending state makes me wonder if Cloudflare itself denies updates when zones are in certain states. |
|
Since we have no reliable repro for this bug, I've opened #1015 to make the deprecation warning a little stronger. In the meantime, for anyone encountering this issue, the path forward here seems to be to use the new |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe what happened
I'm using version
5.42.0of thepulumi-cloudflarepackage in Python.Recently, we've been getting this warning:
My DNS record was successfully created using the
valueargument. However, the bug occurs when updating thevalue.Pulumi detects there's a change:
And proceeds to update the record:
However, on Cloudflare, the record still contains the old value. Nothing has changed.
Changing the code to use
contentinstead ofvalue- solves the issue and the record is indeed updated on Cloudflare.This behaviour is very misleading, as the warning might seem benign at first glance.
I think the warning should at the very least include a message that DNS records with
valueargument can be created but CANNOT be updated.Sample program
Log output
No response
Affected Resource(s)
No response
Output of
pulumi aboutAdditional 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: