mikhailshilkov
commented
11 months ago Sorry for a long delay with response, I needed to change the setup of my Cloudflare test account.
I was able to reproduce the error. I used this sample program to provision a ruleset:
import * as pulumi from "@pulumi/pulumi";
import * as cloudflare from "@pulumi/cloudflare";
const example = new cloudflare.Zone("example", {
accountId: "<account id>",
zone: "test-mikhail-example.com",
});
new cloudflare.Ruleset("domain-rate-limit", {
zoneId: example.id,
name: "transform rule for URI path",
description: "change the URI path to a new static path",
kind: "zone",
phase: "http_request_transform",
rules: [{
action: "rewrite",
actionParameters: {
uri: {
path: {
value: "/my-new-route"
}
}
},
expression: "(http.host eq \"example.com\" and http.request.uri.path eq \"/old-path\")",
description: "example URI path transform rule",
enabled: true,
}]
});and then imported the same ruleset. I got the same result. It looks like we get an almost entirely empty state from the Read operation:
Marshaling property for RPC[newState]: accountId={<account id>}
Marshaling property for RPC[newState]: id={<ruleset id>}
Marshaling property for RPC[newState]: rules={[]}is all I can see.
Something is odd on our side here, needs further debugging. Note that this is a TFPF resource.
ami-descope
zbuchheit
t0yv0
iwahbe
What happened?
I import a ruleset for WAF successfuly, now when I run pulumi up again it wants to replace it, but its exists so it fails
importing ❯ pulumi import cloudflare:index/ruleset:Ruleset domain-rate-limit zones/b0568fbe68169ce1aec3c6f82fca4d6b/be7027900a384d6b9a83d67ae4e13f83 --protect=false
worth mentioning that the rules are empty when i check the state after import
running pulumi up
Example
Output of
pulumi aboutpulumi about CLI Version 3.92.0 Go Version go1.21.3 Go Compiler gc
Plugins NAME VERSION nodejs unknown
Host OS darwin Version 13.6 Arch arm64
This project is written in nodejs: executable='/opt/homebrew/bin/node' version='v20.5.1'
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).