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

Hi all, question about `output.ApplyT`. How do you error handle with it in the Golang SDK?

I’d rather not panic if I can help it. Docs don’t say a ton <https://pkg.go.dev/github.com/pulumi/pulumi/sdk/v3/go/pulumi#OutputState.ApplyT>

Do you mean not panic when you do type assertion like
```intOutput := stringOutput.ApplyT(func(v string) int {
    return len(v)
}).(pulumi.IntOutput)```
or something else?

kiiiinda.

```intOutput := stringOutput.ApplyT(func(v string) int {
    i, err := foo(v)
    if err != nil {
        // handle this err somehow
    }
    return len(i)
}).(pulumi.IntOutput)```

something like that is what i’m looking for

how do i handle the err at the outer layer if the subsequent foo(v) call errs

you can just return an error from the internal func:

```intOutput := stringOutput.ApplyT(func(v string) (int, error) {
    i, err := foo(v)
    if err != nil {
        // handle this err somehow
    }
    return len(i)
}).(pulumi.IntOutput)```

Ah, I think the problem is I was returning an error as the first and only arg. didn’t realize that part of the output interface was error