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

I know this is not exactly an answer to your question, but could you make those URLs relative?

In this case I cannot.  :disappointed: Good idea though. I did figure out an alternative solution, but I am still curious if there is a formal solution for this kind of problem. I can imagine declarative nature of things may make it not possible though.

Yeah, I ran into this before, there are some cases where the underlying Terraform provider bundles some things into one resource that should really be separate resources. IMO AppSetting is one that people commonly run into.

Would be so much better if AppSetting was a separate resource.

I can’t think of any solutions besides hard-coding the knowledge of what the hostname is going to be (in practice the hostname is predictable), or use a custom domain name for your web app.

`$"{baseName]-<http://api-app.azurewebsites.net|api-app.azurewebsites.net>"` would get you the correct result.

That's exactly the alternative we ended up going with. Which actually is a bit more desirable, but meant less MVP for the current work.  Post that solution it was more of an intellectual curiosity. Thanks for replying to me!

/facepalm. That's a great idea. Although wouldn't pulumi add an additional id on that?

Not if you specify the `Name` property of the resource yourself.

I hate the random suffix personally, so I always include the stack name in my resource names instead.

I learned something new. That's going to make a big difference in a few ways. Thanks Daniel!