service-fabric-cli
service-fabric-cli copied to clipboard
Invalid or incorrect application packages will result in 500 errors during `application upgrade`
If there's a mistake in my application package, such as invalid parameter names, or changes in settings that are not allowed, sfctl application upgrade responds with a 500 error message. This is counter-intuitive since a 400 error message is expected when clients send invalid requests or invalid application packages.
Furthermore, there are no details on what is wrong with the application package that was provisioned.
Same here. How can we even think about what might be wrong if just a 500 error comes back? When I do the request manually I get a 200 one. Strange.