Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 446169

Summary:	Missing services should not fail the deployment by default
Product:	[ECD] Orion	Reporter:	Maciej Bendkowski <maciej.bendkowski>
Component:	Deployment	Assignee:	Project Inbox <orion.server-inbox>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	enhancement
Priority:	P4	CC:	arthorne.eclipse, mamacdon, Szymon.Brandys
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Maciej Bendkowski

2014-10-07 09:58:05 EDT

Consider a case when a user creates a Cloud Foundry application with a service which gets deleted after some time, e.g. by accident. Currently, re-deploying the application will get the routes, bits, etc. updated but will fail at binding the service. It follows that the application will not get started. I imagine it would be nice to ask the user whether to start the application anyway or not after we figure out that we can not bind the service to the application.

Comment 1 Mark Macdonald

2015-05-08 13:58:08 EDT

Couldn't reproduce this problem. I tried this:
1. deploy myapp, bound to service "cloudant"
2. cf unbind-service myapp cloudant
3. cf delete-service cloudant
4. Deploy the app again from the web IDE.

The deploy succceeded, even though the app's manifest still references the deleted service.