In general, containers should be considered immutable,
as mentioned in our best practices documentation. To that end, in the most recent dev codeline of Autofac (not yet published) we've marked ContainerBuilder.Update obsolete and intend to remove it in a distant (year or more) future update. In the meantime
Autofac issue #811 discusses why this is the case - why updating a container isn't a good idea, why it's not so easy to just fix things. That discussion has the same relevance here - why you can't/shouldn't update a tenant scope. Rather than repeat all of that here,
go read the issue to see that explanation.
What I could imagine supporting, instead of updating a tenant scope, is the ability to remove an existing tenant scope to allow it to be reconfigured. The application logic would be:
- Remove the specific tenant scope that needs to change from the multitenant container.
- Reconfigure the tenant's registrations, this time with the updated values.
If you think something like that is interesting, I'd recommend
filing an issue with Autofac.Multitenant for an enhancement. Once we have an issue, we can talk about how it might work and we can start accepting pull requests.