Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Allow 'UseDevelopmentStorage=true' in the storage connection string #375

Closed
huguesv opened this issue Jun 1, 2015 · 1 comment
Closed

Allow 'UseDevelopmentStorage=true' in the storage connection string #375

huguesv opened this issue Jun 1, 2015 · 1 comment
Labels
feature-request This issue requires a new behavior in the product in order be resolved. Service Attention Workflow: This issue is responsible by Azure service team. Storage Storage Service (Queues, Blobs, Files)

Comments

@huguesv
Copy link
Contributor

huguesv commented Jun 1, 2015

Right now the only way to run in storage emulator is to pass None for both account key/name, and set the EMULATED env variable. We should allow setting that in the connection string, like node.js storage sdk.
@huguesv huguesv added feature-request This issue requires a new behavior in the product in order be resolved. Storage Storage Service (Queues, Blobs, Files) labels Jun 1, 2015
@huguesv huguesv mentioned this issue Aug 5, 2015
Closed
@crwilcox
Copy link
Contributor

Issue Migrated to Azure/azure-storage-python#6

@crwilcox crwilcox mentioned this issue Aug 19, 2015
Closed
@bsiegel bsiegel added the Service Attention Workflow: This issue is responsible by Azure service team. label Sep 26, 2018
@jongio jongio mentioned this issue Feb 27, 2020
Closed
@github-actions github-actions bot locked and limited conversation to collaborators Apr 13, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
feature-request This issue requires a new behavior in the product in order be resolved. Service Attention Workflow: This issue is responsible by Azure service team. Storage Storage Service (Queues, Blobs, Files)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@bsiegel @crwilcox @huguesv