How can I unset the optional value that have been set before? I am using SentryProvider (just in case it matters) consider following situation: schema:

{ val?: number }

create:

const s = { val: 1 }

now I no want

val

to be

undefined

because SentryProvider has an internal functionality depends on the

undefined

value. update:

const s = { val: undefined }

the problem is that pulumi won’t pick this change up and does nothing, leaving the original value intact. What can I do in this case?

What is SentryProvider? Do you mean

sentry.Provider

? I can't see an Input on sentry.Provider that takes an optional value, so I can't check the code. Is it a provider or a cloud resource that's showing this behaviour?

It is this resource https://www.pulumi.com/registry/packages/sentry/api-docs/sentryissuealert/#inputs The problematic property is

environment

. official sentry API says it is nullable (or optinal) So I checked the terraform provider and found it optional. but optional to pulumi means

undefined

not

null

. So I am digging in the terraform provider of the version 11, that’s what pulumi uses https://registry.terraform.io/providers/jianyuan/sentry/0.11.2/docs/resources/issue_alert#environment-6 and it is optional even there. It is still optional in even in the latest version And the new version

14.x

is based on open API spec https://registry.terraform.io/providers/jianyuan/sentry/latest/docs/resources/issue_alert#environment-2 Which makes me wonder if the terraform provider works as expected and it is messed up on pulumi side or not.

Have you tried setting it to null?

the type is

pulumi.Input<string> | undefined

not

null

Yep. Nulls suck. That API seems to be ORing all those fields together, is that right? If any issue matches, then the alert is sent. And you just want to ignore the

environment

value and send the alert no matter what it is. Can you use the

filter

property and set it to something that always matches everything? Or something that always matches what you want.

I could do something like that and use

replaceOnChanges

to recreate the whole resource

Yep that'd work, probably

And I did try to pass

null as any

to avoid type checking. IMO there’s somewhere a nullcheck for nullish values because the same behaviour can be expected with

null, undefined, ""

- no changes to state

I don't think

null as any

would work the same way as going to JS, and it might work. However I'd say the other solution would be much simpler to implement

The API is so bugged that you can use the same condition multiple times 🏭 🤦 so I set

replaceOnChanges:["conditions"]

and

environment: undefined

and this has caused the replacement and expected behaviour.