I did end up running into a few purrl issue, but I think it's just me. If anyone way more experienced has thoughts, would love some insight. 1. Can I make a Purrl resource that isn't persisted to the stack? edit: it seems

ignoreChanges

on the Purrl resource does what I'm looking for 2. What's the best pattern for getting the Purrl

response

object and turning it into JSON? Should I be doing

pulumi.parseJson

, or is there a static method on Purrl I missed 3. What's the best practice (in your opinion) for bundling up the 7-10 Purrl's I need to do? edit: Think I solved this w/ a custom resource 4. When you don't match a response code, is there an

errorResponse

or other location the response text is located for logging purposes? AFAIK

response

and

deleteResponse

only get set on a matching response code.

Hi @dry-pilot-49577, Sorry for the late reply. Busy week at KubeCon. 4. There is an PR i am reviewing currently -> https://github.com/pulumiverse/pulumi-purrl/pull/75 2.

ParseJson

should be the key here.

I did run into one other snag. Does Purrl have a placeholder syntax for the resource id? Ideally the deleteUrl should be something like

<https://api.service.com/rest/object/{id}>

I worked around it by making an API call out of pulumi, but wanted to make sure I didn't miss something.

Thats a good feature request indeed.