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

[BUG/QUESTION] Where is NameValidator? #15016

Closed
hansmbakker opened this issue Sep 9, 2020 · 3 comments
Closed

[BUG/QUESTION] Where is NameValidator? #15016

hansmbakker opened this issue Sep 9, 2020 · 3 comments
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. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team. Storage Storage Service (Queues, Blobs, Files)

Comments

@hansmbakker
Copy link

Query/Question
Microsoft.Azure.Storage.Common had the useful NameValidator class. I can't find the same functionality in the new Azure.Storage client library.

Environment:

  • Name and version of the Library package used: Azure.Storage.Blobs, major version 12
@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 Sep 9, 2020
@jsquire jsquire added Client This issue points to a problem in the data-plane of the library. 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) labels Sep 9, 2020
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Sep 9, 2020
@jsquire
Copy link
Member

jsquire commented Sep 9, 2020

Thank you for your feedback. Tagging and routing to the team best able to assist.

@ghost
Copy link

ghost commented Sep 9, 2020

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

@amnguye
Copy link
Member

amnguye commented Sep 9, 2020

We currently don't support it in v12. This issue is a duplicate of issue #9611

@amnguye amnguye closed this as completed Sep 9, 2020
openapi-sdkautomation bot pushed a commit to AzureSDKAutomation/azure-sdk-for-net that referenced this issue Jul 2, 2021
CodeGen from PR 15016 in Azure/azure-rest-api-specs
e3b610e 
Changes to fix the Resource Provider name casing issue for Azure Postgres, MySQL and MariaDB  (Azure#15016)

* Changes to fix the Resource provided name casing issue for Azure Postgres, MySQL and MariaDB services

* Changes to fix the Resource provided name casing issue for Azure Postgres, MySQL and MariaDB services

* Revert "Changes to fix the Resource provided name casing issue for Azure Postgres, MySQL and MariaDB services"

This reverts commit ecc38dc560b77de750350143fd80bdd6e3823882.
openapi-sdkautomation bot pushed a commit to AzureSDKAutomation/azure-sdk-for-net that referenced this issue Jul 2, 2021
CodeGen from PR 15016 in Azure/azure-rest-api-specs
3637417 
Changes to fix the Resource Provider name casing issue for Azure Postgres, MySQL and MariaDB  (Azure#15016)

* Changes to fix the Resource provided name casing issue for Azure Postgres, MySQL and MariaDB services

* Changes to fix the Resource provided name casing issue for Azure Postgres, MySQL and MariaDB services

* Revert "Changes to fix the Resource provided name casing issue for Azure Postgres, MySQL and MariaDB services"

This reverts commit ecc38dc560b77de750350143fd80bdd6e3823882.
@github-actions github-actions bot locked and limited conversation to collaborators Mar 28, 2023
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. customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that 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
@jsquire @hansmbakker @amnguye