Let's say I create a servicebus namespace, queue, topics and subscriptions through pulumi. What is the best way to access the service bus from an application you write. Ideally I wouldn't like to hard code the name in this place since the name might be changed when deploying to a new stack. Do I in the application read the actual names from the pulumi output? Or is this one of the scenarios where you override the name of the resource to not include the suffix?

How do you deploy your application which needs to connect to the servicebus? In our case with container based deployments (azure container instances or Kubernetes deployments) we inject those environment specific values using environment variables or indirectly using Kubernetes secrets that get mapped to env vars in the container. Therefore the application is built in a way that it allows overwriting configurations via env vars. See https://12factor.net/config

That is actually pretty cool, should have thought about that 🙂. I did it the naive way with just setting the

Name

in the args properties so I know what it will be called. I like your approach better.

Don’t hesitate to ask if you want to learn about what worked well for us and what not. Happy to share some experiences.

@rhythmic-finland-36256 I accidently answered in the wrong channel. Awesome tips and got something working fairly simple.