cloudfoundry / cloudfoundry/multiapps-controller

support for multiple processes

Open
#1,365 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Java
Stars
65
Forks
41
Avg merge
1d 5h
Merged PRs (30d)
11

Description

Dear team,

is there a plan that MTA supports processes for CF apps, as it supported by CF manifests see https://docs.cloudfoundry.org/devguide/multiple-processes.html#manifest ?

I couldn't identify where is the issue.

I have a manifest.yaml

---
applications:
- name: app
  path: .
  buildpacks:
  - nodejs_buildpack
  processes:
  - type: web
    command: node server.js
  - type: worker
    command: node worker.js
    health-check-type: process
    instances: 1

and cf push works as expected.

With following mta.yaml

_schema-version: 3.3.0
ID: app
version: 1.0.0

modules:
  - name: app
    type: nodejs
    path: .
    build-parameters:
      ignore:
      - mta_archives/
    parameters:
      processes:
        - type: web
          command: node server.js
        - type: worker
          command: node worker.js
          health-check-type: process
          instances: 1

and deploying using

mbt build 
cf deploy mta_archives/app_1.0.0.mtar

The application has only web process (no worker).

Thanks,
Adam

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing the Cloud Foundry manifest's processes behavior with the processes section in mta.yaml, then trace how the controller handles module parameters during cf deploy. Use mbt build and cf deploy with the supplied example to verify that both web and worker processes are created, including the worker's command, health check, and instance count.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
cloud, devops
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.