search

Azure / azure-cli

Azure Command-Line Interface
MIT License
3.92k stars 2.89k forks source link

Notification Hub - Can't update Google API key #23644

Open etiennehucklemarchand opened 1 year ago

etiennehucklemarchand commented 1 year ago

Issue We're using an Azure CLI script to update the Google API key of this Notification Hub. However, az notification-hub credential gcm update started randomly "failing". This Azure CLI command doesn't seem to have a timeout; it just spins forever.

az notification-hub credential gcm update --resource-group $resourceGroup --notification-hub-name $notificationHub --namespace-name $hubNamespace --google-api-key $googleKey

We've contacted Azure support about this and they told us that, to perform this operation, Azure contacts Google's servers to validate those gcm credentials. This is a synchronous operation. Google is taking 85 seconds to perform that validation, and Azure is timing out after 60 seconds, so the request doesn't get through.

Suggestion Adding a timeout parameter or simply timeout after ~60 seconds, instead of running forever.

ghost commented 1 year ago

Thank you for your feedback. This has been routed to the support team for assistance.

yonzhan commented 1 year ago

route to CXP team

ghost commented 1 year ago

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

Issue Details
**Issue** We're using an Azure CLI script to update the Google API key of this Notification Hub. However, `az notification-hub credential gcm update` started randomly "failing". This Azure CLI command doesn't seem to have a timeout; it just spins forever. `az notification-hub credential gcm update --resource-group $resourceGroup --notification-hub-name $notificationHub --namespace-name $hubNamespace --google-api-key $googleKey` We've contacted Azure support about this and they told us that, to perform this operation, Azure contacts Google's servers to validate those gcm credentials. This is a synchronous operation. Google is taking 85 seconds to perform that validation, and Azure is timing out after 60 seconds, so the request doesn't get through. **Suggestion** Adding a timeout parameter or simply timeout after ~60 seconds, instead of running forever.
Author: etiennehucklemarchand
Assignees: -
Labels: `Service Attention`, `Notification Hub`, `customer-reported`, `feature-request`
Milestone: -
navba-MSFT commented 1 year ago

Adding Service team to look into this ask.

@tjsomasundaram-zz Could you please look into this ask and provide an update ?