Option for providing a path to persist data from the Azurite container

[aaronpowell]

Fixes #1533

Microsoft Reviewers: Open in CodeFlow

[davidfowl]

Why not a callback with the container resource? That way we don’t need to come back again when the next feature request comes in.

[mitchdenny]

There is no container resource, this simply adds an annotation. Any resource can be a container if it has the right annotation. I think having this as a parameter on UseEmulator(...) feels right - when you are using this method you are already in the context of configuring the emulator which supports this resource.

I think we should talk about options/settings patterns for builder extension methods in the offsite though - so perhaps we should hold this until next week (even though I think this is probably the right solution).

[aaronpowell]

Yep, as @mitchdenny notes, we don't have a ContainerResource type available here, so we can't use the existing extension method, which is why I went with the parameters.

[davidfowl]

Ah I see.