Azure / Azure/Azurite

No way to create new default configuration for Azurite

Open
#1,689 9 comments 0 reactions 1 assignee Claimed by @blueww View on GitHub
enhancement Visual Studio
Dominant language
TypeScript
Stars
2.3k
Forks
393
Avg merge
1d 20h
Merged PRs (30d)
36

Description

### Which service(blob, file, queue, table) does this issue concern?
All services

### Which version of the Azurite was used?
3.18.0

### Where do you get Azurite? (npm, DockerHub, NuGet, Visual Studio Code Extension)
Visual Studio 2022

### What's the Node.js version?
N/A

### What problem was encountered?
There doesn't appear to be a way to configure Azurite from within VS2022, or to persist changes to Azurite behavior to a default configuration. When using VS2022 to develop/debug Azure functions, VS2022 automatically starts Azurite with the default configuration running on ports 10000/10001/10002. If your system already uses any of those ports, Azurite won't work. You have to launch Azurite externally with the port overrides, before debugging the Azure function. It would be nice if you could persist any configuration overrides to a configuration file that would be automatically invoked at the next launch, ideally picked up when VS2022 automatically starts Azurite.

### Steps to reproduce the issue?
N/A

### Have you found a mitigation/solution?
Yes, launch Azurite from a Command Windows with specific arguments (prior to debugging), and customize the app connection string to reference those custom settings

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.