This message was deleted.

Pulumi does that intentionally and you usually want that suffix, as it prevents collisions between multiple instances/stacks that are running in the same environment. If you are asserting that your current environment (not stack, but project/account/etc. depending on your provider) must never have more than one instance of this resource, even if it talks to different things (i.e., you have multiple separate instances of your application in the same runtime environment, like special instances for certain customers), then what you want is OK, but given that Pulumi encourages you to operate on outputs from stacks rather than hard-coded values, it rarely should matter to you in a hands-on-keyboard way.

I understand your explanation, but I still need to set the trigger url the way I want to. And

httpsTriggerUrl

doesn't seem to fix it

That sounds like a usability bug. Maybe file an issue?

No, I was actually wrong concerning

httpsTriggerUrl

: it's only an output and not a value that can be set