Hello, Pulumi community! I need some help with a problem I’m facing while using Pulumi with Kanbanize. I’ve published my code to a public GitHub repo to make it easier for you to see the problem: https://github.com/artur-shlyapnikov/pulumi-kanbanize, There is also a ready-made stack with the API key, so that you can run

pulumi up

right away. I’ve implemented a custom Pulumi provider for Kanbanize boards. The create and update methods work just fine, but I’m having trouble with the delete method. For some reason, it doesn’t pass the API key to Kanbanize, resulting in an error. I’ve tried debugging the issue and logging the headers, but I can’t seem to figure out why the API key is not being passed. Any help or insights on how to resolve this issue would be greatly appreciated. Thank you in advance!

The props passed to delete are the outputs of the resource not the inputs. Because "create" and "update" don't return the apikey in their props (which define the outputs) it's not passed into "delete"

Thanks! But despite explicitly passing the apiKey in the outputs of the create, update, and archive functions, the issue remains unresolved. Here’s a link to the commit.

Are the other properties being passed to delete? Is it just apiKey missing? If you run

pulumi stack export

what properties does the "outputs" block contain for the board resource?

If you run

pulumi stack export

what properties does the “outputs” block contain for the board resource?

I removed the

provider

filed for clarity , as it contains the whole compiled code:

❯ pulumi stack export | jq '.deployment.resources[] | select(.id == "25") | .outputs | del(.__provider)'
{
  "description": "",
  "is_archived": 0,
  "name": "AAA",
  "workspace_id": 2
}

apiKey is not in the output

Are you sure the resource has actually rerun Create/Update since you changed the code to return apiKey from those methods?

No, I’m not sure. Looking at the output of the command above, I guess I figured out the main point that was getting in my way of debugging: for custom resources, pulumi output and input contain the full provider code. Consequently, the previous run must contain the correct code.

Consequently, the previous run must contain the correct code

Only for destroy. For Diff/Update/Create it will always use the latest code from the program. But the engine only calls Create/Update if it thinks there's a diff and has you haven't implemented a Diff method I think the default is no diff (probably not the best default given cases like this, but back compatibility means hard to change)

But the engine only calls Create/Update if it thinks there’s a diff and has you haven’t implemented a Diff method I think the default is no diff

And now I finally get it!

no worries, the documentations a bit lacking here so def a good use of slack 🙂