No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

This is caused because you're calling `stringify()` on a an object that contains outputs. You're calling `apply()` on _k0sconfig_ which is necessary, but _k0sconfig_ itself contains outputs.

You have a few options here, such as delegating to Pulumi like Stew suggests. Or adding parameters to `all()` (are apiVersion and kind outputs?) _and_ nesting calls to `apply()` (are n.role and n.ip outputs?).

Or you could find the nested-unwrapping logic that Pulumi uses and see if you can call it yourself, or rewrite it.

Looking at your `k0sconfig` declaration, I see `k0sctrl.apiVersion` and `k0sctrl.kind` inside the body of the function - are those outputs as well?

Great minds think alike :slightly_smiling_face: That was my question 2 lines up :point_up:

yep, here's a worked example:

<https://gist.github.com/AaronFriel/fa4d88781f339c2c26791a08b9c50c0e>

It's possibly cleaner (not sure on how it looks in Python) to update `pulumi.all()` to have `nodes` and `k0sctrl.kind` as parameters. Achieves the same thing without having to await a promise inside the block.

We're on the same ideas-train today! :raised_hands:

Here's what a potential fix would look like: <https://gist.github.com/AaronFriel/fa4d88781f339c2c26791a08b9c50c0e#file-example-ts-L57-L71>

Not sure why I thought all this was in Python.. I'm answering too many questions, maybe...