Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

from terraform-provider-cloudflare.

the issue you've raised here is not a provider issue but the way the rulesets engine is designed and has entitlement restrictions. you should reach out to your account team to have them address this.

from terraform-provider-cloudflare.

the issue you've raised here is not a provider issue but the way the rulesets engine is designed and has entitlement restrictions. you should reach out to your account team to have them address this.

@jacobbednarz Thanks for your comment. IMHO if that was something related on my account or due to entitlement restrictions, I would not be able to create/activate the ruleset via webUI, which I can. I understand that the error is coming from the API, but the fact that I can activate it via webUI seems to point to the code.

I'll be happy to raise a ticket with the support team, but the fact that I can create and enable the ruleset via webUI does change anything on your statement?

Thanks!

from terraform-provider-cloudflare.

depending on what you are doing the UI will consolidate it into a single root ruleset for the phase. you can do the same thing in terraform but you'll need to fix your configuration to match that behaviour instead of what you are doing now (trying to create multiples through your module). it still isn't a bug and a restriction of ERE. full docs are available at https://developers.cloudflare.com/ruleset-engine/

there are mentions of this and debugging steps in #2004 as well.

from terraform-provider-cloudflare.

@jacobbednarz just to provide closure, we were able to get this addressed. The problem was not on our Terraform code/logic but on a bad API data which we believe was a bad leftover during the attempts reported at #2970.

As mentioned on the #2004, the data was not being displayed an the UI which was causing a trigger a generic API exception.

Basically we manually forced a DELETE and then the same Terraform code worked as expected.

❯ curl --request DELETE https://api.cloudflare.com/client/v4/accounts/XXXXXX/rulesets/5xxxxxx \
[....]

Thanks for your help!

from terraform-provider-cloudflare.