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

Storage Blob/FileShare/FileDataLake/Queue - enable min-max testing #17888

Closed
jeremymeng opened this issue Sep 27, 2021 · 1 comment
Closed

Storage Blob/FileShare/FileDataLake/Queue - enable min-max testing #17888

jeremymeng opened this issue Sep 27, 2021 · 1 comment
Labels
Client This issue points to a problem in the data-plane of the library. Storage Storage Service (Queues, Blobs, Files)

Comments

@jeremymeng
Copy link
Member

jeremymeng commented Sep 27, 2021 •
edited
Loading

See #17830 for more details
@ghost ghost added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Sep 27, 2021
@jeremymeng jeremymeng added the Client This issue points to a problem in the data-plane of the library. label Sep 27, 2021
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Sep 27, 2021
@jeremymeng jeremymeng added the Storage Storage Service (Queues, Blobs, Files) label Sep 27, 2021
@EmmaZhu EmmaZhu added this to the Backlog milestone Dec 14, 2021
@KarishmaGhiya KarishmaGhiya mentioned this issue Dec 21, 2021
Closed
15 tasks
openapi-sdkautomation bot pushed a commit to AzureSDKAutomation/azure-sdk-for-js that referenced this issue Mar 8, 2022
CodeGen from PR 17888 in Azure/azure-rest-api-specs
9ef77f1 
Adding Lots by Customer (Azure#17888)

* Adding Lots by Customer

* Prettier fix

* Fixing Semantic

* Fixing Semantic

* Fixing Semantic

* Update consumption.json

* Fixing PR comments

* Deleting properties not allowed
@github-actions GitHub Actions
Copy link

Hi @jeremymeng, 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.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 15, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Mar 15, 2024
@xirzec xirzec removed this from the Backlog milestone May 7, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Client This issue points to a problem in the data-plane of the library. Storage Storage Service (Queues, Blobs, Files)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@xirzec @EmmaZhu @jeremymeng