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
Cloudflare DNS Record GET Issues #26
Comments
I'm assuming this is an issue with the Terraform provider and not Pulumi. Here's resourceCloudflareRecordRead Here's resourceCloudflareRecordImport I'm assuming the issue is to do with the read function - import seems to handle it correctly just glancing at the code. Unfortunately I don't know how this is all wired together well enough to debug resourceCloudflareRecordRead :( If this issue should instead be made on the TF repo, let me know! |
Just experienced this, while attempting to import a record into a stack. At first I set the
Results in: cloudflare:index:Record (a-record): But then specifying the zone name:
results in...
It appears to be routing to |
@stack72 Just checking in on this, any updates? |
I have updated the provider. The import should be of the format Can you try an upgrade and see if that works for you? P. |
Hi @damianh Please can you tell me if this is still a problem for you since the 1.0.0 release of the provider? P. |
Going to close this out for now - I've not heard if this can be re-created with 1.0.0 of the provider. Please let me know if this is still the case |
Works here, cheers. |
I think there's an issue with the Cloudflare DNS Record GET function.
Tested on v0.17.1 and v0.17.8
https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/cloudflare/#Record-get
According to https://api.cloudflare.com/#dns-records-for-a-zone-dns-record-details
We need to be generating this URI
/zones/<zone-id>/dns_records/<record-id>
Currently,
Will generate the following error
It looks like the issue here is that the
<zoneId>/<recordId>
is being directly passed to the URI as the<record-id>
instead of splitting it and resolving the ZoneID and removing it.The text was updated successfully, but these errors were encountered: