-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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.
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
CheckPrivateLinkServiceVisibility api in network has changed #11627
Comments
That should be a critical bug fix in Swagger, not something you workaround here, just my two cents. CC @RodgeFu |
+1, let's wait for network team to confirm the behavior change and work with them to fix the swagger. thanks. |
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @aznetsuppgithub. Issue meta data
|
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @privlinksuppgithub. Issue meta data
|
[Hub Generated] Review request for Microsoft.Logic to add version stable/2019-05-01 (Azure#11627) * Adding integration service environment encryption configuration details to Logic spec * Correcting json format errors * Correcting json formats * Updating examples * Fixing encryption key properties definition Co-authored-by: Rama Krishna Rayudu <[email protected]>
@00Kai0 could you check if this is still reproable? |
Hi @00Kai0. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text “ |
Hi @00Kai0, since you haven’t asked that we “ |
This checkPrivateLinkServiceVisibility api returned an unexcepted code 202. I think it has been change to a LRO method, but hasn't been updated in swagger.
The text was updated successfully, but these errors were encountered: