Comment 3 for bug 1357220

Thanks for the response Ekaterina :)

I think the ideal solution is one where the user clearly knows that he/she can perform an action like deploying. Currently the status says "Configuring" which is confusing as it leads one to believe that they need to wait until the configuring is completed, but there is no configuring occurring in the background. So when a user adds a component and the component is finished getting added, the API returns status "pending". The other statuses you suggested (Configure, Composition) are not ideal either as they are not clear (at least not in English). If the "pending" status means that the component has been added then I'd suggest we set the status to "Ready to deploy" or "Component added" to indicate the true state to the user that they can act on. "Configuring" makes the user think they need to wait for the configuring to finish before they can deploy, "Configure" makes the user think they need to click on the configure status and configure something before they can deploy (not true). "Ready to deploy" or "Component added" make the most sense to me.

What do you think?