Project: duracloud
Issue DURACLOUD-924: Instance not initialized call should return something other than a 503
Each of the DuraCloud apps currently responds to a /init REST call with either a 200 if the app is initialized and ready for use or a 503 if the app is available but not yet initialized. This task is to update this to change the 503 to another code. The reason is that Apache also returns 503 responses as a DuraCloud instance is starting when it is not yet able to make a connection to Tomcat. This results in the Management Console thinking that an instance is ready to be initialized when it is not yet available. Note that this change will require a companion change in the MC to ensure that the correct HTTP code is expected on init.
Story points: 1