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

[Plan-Build] Composite Plan feature #2661

Closed
reset opened this issue Jun 27, 2017 · 1 comment
Closed

[Plan-Build] Composite Plan feature #2661

reset opened this issue Jun 27, 2017 · 1 comment
Labels
Focus :Plan Build Type: Feature Issues that describe a new desired feature

Comments

@reset
Copy link
Collaborator

reset commented Jun 27, 2017

Add a feature to the Plan syntax to describe a service which is only of use when started with one or more additional services within the same Supervisor. An example of this is the relationship between a proxy and api server or php applications.

This will be a new pkg variable or a slightly different file name for a plan. The generated package is a "pointer" to other packages and forces all operations to be atomic - that is, if you start the composite package then all services it points to will also be started.

In the composite plan we will also need to map it's pkg_binds and pkg_exports to the packages it is composed of. This will require some small modifications to service rumors to identify a "composite package".

See #2520 for the initial discussion start

@smith
Copy link
Contributor

smith commented Aug 28, 2017

More detail is in #2902.

@smith smith closed this as completed Aug 28, 2017
@christophermaier christophermaier added Type: Feature Issues that describe a new desired feature and removed C-feature labels Jul 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Focus :Plan Build Type: Feature Issues that describe a new desired feature
Projects
None yet
Development

No branches or pull requests

3 participants