I’m not entirely sure if the question is geared towards Service Bus connection string or any setting in general. I’ll provide both.
For a single configuration that needs to be different per team member, I found environment variables to be very helpful. It’s secure, specific to the machine it’s running on, and nothing is checked into the repository. With the .NET Core configuration API (Providers) that becomes even easier as settings can be read from files, environment variables, or command-line arguments.
Which brings the second answer, if you need to manage all the settings per user. You could still do environment variables, but that could be a lot. Another option is to have a
setting.json file as a template for all the keys that .NET Core Configuration API can handle, as well as local versions (per developer/environment) that are not checked in. In higher environments
setting.json could be configured with the values relevant to the environment in use.
And then there’s another option. Since you’re already consuming Azure resources, have you had a chance to look at Azure Application Configuration service? The nice thing about it is that it allows multiple environments for the same keys. Which means you could have each developer have its own prefix with the values unique to them, including production. An environment variable such as
environment could indicate what prefix to use,
Hope that helps.