The code showed in item "4" on the "Open and edit the solution" section does not work as indicated. In case a 429 is returned by keyVault, the code won't actually retry as suggested. That's because the try/catch block is outside of the loop. In addition, the variable "waitTime" is not used anywhere in the code.
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@grlima Thanks for the feedback! We are currently investigating and will update you shortly.
@grlima
Thanks for pointing this out. As per our investigation we are also able to get the same result.
@prashanthyv
Could the code sample as mentioned by the user be re-checked as we are also not able to get it working ?
Hi @grlima - Please look out for the next PR.
Thanks
Hi @prashanthyv @YutongTie-MSFT @grlima
Has this problem been fixed?
Yes it has
@prashanthyv so the above code sample now works as expected? I just tried it and it appears to get the secret twice which doesn't seem right. It gets it once from the original getAsync then gets it again in the do while loop.
@developercreativepos - Are you looking at this page - https://docs.microsoft.com/en-us/azure/key-vault/key-vault-ovw-throttling ?
Thanks. Will fix that
Awesome, thank you. Do you have an ETA for when it will be updated?
Is there a way to subscribe to this issue, either on Microsoft or GitHub?
@JohnBoncek - The fix should be available by tomorrow
Hi guys, well the variables: retry and retries are not being used in this tutorial (https://docs.microsoft.com/en-us/azure/key-vault/tutorial-net-create-vault-azure-web-app), there are no retries here.
@barclayn do you know the status on this tutorial?
Guys, I also do not understand how this code works. Unused functions, bogus retry variables.
Better remove than keep and confuse.
Code is updated with retries. #please-close
Most helpful comment
Guys, I also do not understand how this code works. Unused functions, bogus retry variables.
Better remove than keep and confuse.