-
Notifications
You must be signed in to change notification settings - Fork 246
Azure HPC Cache name is limited to 31 characters instead of 80 #2759
Comments
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @xgithubtriage |
@jsmartt Hello. Our SDK is auto-generated. The root cause is that service team set this limitation in their swagger spec. We have to fix it in the swagger spec first. I add service attention to invite correct team. But it's better to open a PR in this repo https://github.com/Azure/azure-rest-api-specs/ |
Thanks @myronfanqiu. I did open a PR on that repo, but it looks like it needs some help from some MSFT folks to fix build/validation issues and enable SDK automation. |
Could you give me the PR link? |
It's linked just above my comment too, but it's Azure/azure-rest-api-specs#8606 |
Hi @jsmartt thanks for pointing it out. @myronfanqiu There is a new version coming, which has this fix. https://github.com/Azure/azure-rest-api-specs/pull/8403/files |
@romahamu good to know. Once it's merged, you can request a sdk release through https://portal.azure-devex-tools.com/ |
Hi, this issue appears to be resolved, so I'm closing it now. Thanks! |
Many places in this file, there is a regex, validating the name matches the pattern
^[-0-9a-zA-Z_]{1,31}$
. It will prevent any action (including get or create) with a name longer than 31 characters by raising the following error:However, the Azure console shows the following validation:
The API validation allows 80 characters, so I'm guessing this SDK needs updated.
The text was updated successfully, but these errors were encountered: