Skip to content
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

As a service author, I can invoke a service to stop, start, restart, and restage the backing applications associated with a service instance #118

Closed
scottfrederick opened this issue Oct 8, 2018 · 0 comments
Assignees
Labels
accepted feature New feature or request
Milestone

Comments

@scottfrederick
Copy link
Contributor

scottfrederick commented Oct 8, 2018

GIVEN one or more backing apps are configured for a service and plan
THEN a service broker application can auto-wire a service bean that provides methods to start, stop, restart, and restage all backing apps associated with a service instance (as identified by a service instance GUID)

The goal of this feature is to make it easy for implementing brokers to support generic actions as proposed in the OSB API spec, with actions that act on SI-backing applications. With this feature, broker authors would implement the web endpoints (e.g. Controller classes) that respond to external requests, and delegate the work to service beans provided by App Broker.

@scottfrederick scottfrederick added the feature New feature or request label Oct 8, 2018
@scottfrederick scottfrederick changed the title As a service author, I can invoke a service that can stop, start, and restart the backing applications associated with a service instance As a service author, I can invoke a service to stop, start, and restart the backing applications associated with a service instance Oct 8, 2018
@scottfrederick scottfrederick added this to the 1.0.0.M2 milestone Nov 26, 2018
@scottfrederick scottfrederick modified the milestones: 1.0.0.M2, 1.0.0.RC1 Dec 4, 2018
@scottfrederick scottfrederick changed the title As a service author, I can invoke a service to stop, start, and restart the backing applications associated with a service instance As a service author, I can invoke a service to stop, start, restart, and restage the backing applications associated with a service instance Jan 9, 2019
@royclarkson royclarkson self-assigned this Jan 15, 2019
royclarkson added a commit that referenced this issue Mar 13, 2019
This commit adds support to stop, start, restart, and restage the backing
applications associated with a deployed service instance. The management
functions are available from the new `BackingAppManagementService`.

Resolves #118
royclarkson added a commit that referenced this issue Mar 14, 2019
This commit adds support to stop, start, restart, and restage the backing
applications associated with a deployed service instance. The management
functions are available from the new `BackingAppManagementService`.

Resolves #118
royclarkson added a commit that referenced this issue Mar 14, 2019
This commit adds support to stop, start, restart, and restage the backing
applications associated with a deployed service instance. The management
functions are available from the new `BackingAppManagementService`.

Resolves #118
royclarkson added a commit that referenced this issue Mar 15, 2019
This commit adds support to stop, start, restart, and restage the backing
applications associated with a deployed service instance. The management
functions are available from the new `BackingAppManagementService`.

Resolves #118
royclarkson added a commit that referenced this issue Mar 15, 2019
This commit adds support to stop, start, restart, and restage the backing
applications associated with a deployed service instance. The management
functions are available from the new `BackingAppManagementService`.

Resolves #118
@royclarkson royclarkson modified the milestones: 1.0.0.RC1, 1.0.0.M1 Apr 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accepted feature New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants