Allow "startup commands"
- 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?
Blob.
### Which version of the Azurite was used?
3.19.0
### Where do you get Azurite? (npm, DockerHub, NuGet, Visual Studio Code Extension)
DockerHub
### What's the Node.js version?
In Docker image.
### What problem was encountered?
When trying to set up Azurite for my app's functional tests (app uses Azure blob storage), I need to have a few containers created in the storage. The real containers are typically created with Terraform on deployment, the app itself doesn't create the containers.
It would make sense to be able to do a similar thing with Azurite: being able to have a basic "startup commands" feature where the user can list some pre-requisites and Azurite itself creates them.
### Steps to reproduce the issue?
Run Azurite container and use the container `thumbnails`. The container doesn't exists and I can't make Azurite create it when starting up.
### Have you found a mitigation/solution?
Two ways:
1. the app can use its SDK and connection string to create the required containers, but since it otherwise expects them to be pre-existing, this feature would be built for tests only, messing up the application codebase with unrelated infrastructure code
2. use an additional sideloaded container with a standalone SDK client (or `az` CLI tool) to run the commands, this is tricky to coordinate and quite convoluted overall, but seems like the direction which I'll probably take
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.