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
Add support for upcomming RegisterApplicationTypeTimeoutSec parameter in Service Fabric SDK #4496
Comments
Another report https://secure.helpscout.net/conversation/591051539/27588/ Looks like this is actually available now, so implementation could go ahead on our side |
Release Note: Added RegisterApplicationTypeTimeoutSec to Service Fabric deploy step |
This is still persisting. |
@benPearce1 this seems to be done? |
@BharathRahulDS Can you please provide some more information about any issues you might be receiving? |
We support this timeout now in the step, closing this. |
This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately. |
Publish-NewServiceFabricApplication
is callingRegister-ServiceFabricApplicationType
as part of the service fabric deployment, but there is no way to set the timeout forRegister-ServiceFabricApplicationType
.The issue at microsoft/service-fabric-issues#347 indicates that Publish-NewServiceFabricApplication will gain a new parameter called
RegisterApplicationTypeTimeoutSec
that will allow a timeout to be set. This timeout should then be something we expose to resolve errors like the one described at https://secure.helpscout.net/conversation/562991622?folderId=1380316.The text was updated successfully, but these errors were encountered: