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

[FEATURE REQ] Azure.Storage.Blobs - Expose DevelopmentStorageAccount equivalent #11329

Closed
wahyuen opened this issue Apr 15, 2020 · 7 comments
Closed

[FEATURE REQ] Azure.Storage.Blobs - Expose DevelopmentStorageAccount equivalent #11329

wahyuen opened this issue Apr 15, 2020 · 7 comments
Assignees
@amishra-dev
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. feature-request This issue requires a new behavior in the product in order be resolved. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team Service Attention Workflow: This issue is responsible by Azure service team. Storage Storage Service (Queues, Blobs, Files)
Milestone
Backlog

Comments

@wahyuen
Copy link

wahyuen commented Apr 15, 2020

Library or service name.
What library or service is this request related to? [e.g. Azure.Storage.Blobs] Azure.Storage.Blobs

Is your feature request related to a problem? Please describe.
What feature would you like to get added? What problem is it solving?

Previous versions of the SDK exposed out a convenience reference which was useful for local development and integration tests via the following command CloudStorageAccount.DevelopmentStorageAccount

It would be great if the v12 SDK exposed out something similar instead of peopling having to move back to magic strings. This appears to still be referenced inside StorageConnectionString however, this class is currently marked as internal
@ghost ghost added needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Apr 15, 2020
@jsquire jsquire added Client This issue points to a problem in the data-plane of the library. 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) and removed question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Apr 15, 2020
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Apr 15, 2020
@ghost
Copy link

ghost commented Apr 15, 2020

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @xgithubtriage.

@amishra-dev
Copy link
Contributor

Hi @wahyuen
Thanks for the report, we would like to gather further feedback before enabling this back. Meanwhile have you considered Azurite?

@amishra-dev amishra-dev removed the Service Attention Workflow: This issue is responsible by Azure service team. label Apr 17, 2020
@amishra-dev amishra-dev self-assigned this Apr 17, 2020
@wahyuen
Copy link
Author

wahyuen commented Apr 17, 2020

Not at this stage, we are still assessing the viability to upgrade to v12 of the Storage SDK and how this affects our currently development environment and release pipelines.

@amishra-dev
Copy link
Contributor

Ok, let me check with the team and get back to you tomorrow.

@Petermarcu Petermarcu added the Service Attention Workflow: This issue is responsible by Azure service team. label Apr 17, 2020
@ghost
Copy link

ghost commented Apr 17, 2020

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @xgithubtriage.

@jsquire jsquire added this to the Backlog milestone Jun 2, 2020
@jsquire jsquire added the needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team label Jun 2, 2020
@SeanFeldman
Copy link
Contributor

Whenever SDK was redesigned, this should be included. Development account is widely used for local automated verifications and having it as a constant exposed by the SDK was there for a very long time. Please add it and don't force customers to redefine what the SDK should be exposing.

@SeanFeldman SeanFeldman mentioned this issue Jun 24, 2020
Closed
@danegsta danegsta mentioned this issue Sep 1, 2022
Closed
@JimSuplizio
Copy link
Member

Hi @wahyuen, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.

@JimSuplizio JimSuplizio closed this as not planned Won't fix, can't repro, duplicate, stale Mar 5, 2024
@Azure Azure locked and limited conversation to collaborators Mar 5, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@amishra-dev amishra-dev

Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. feature-request This issue requires a new behavior in the product in order be resolved. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team Service Attention Workflow: This issue is responsible by Azure service team. Storage Storage Service (Queues, Blobs, Files)
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
6 participants
@jsquire @SeanFeldman @wahyuen @Petermarcu @amishra-dev @JimSuplizio