Expose partial deployment module/resource selection via the deploy service REST API

Aperta
#1,945 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
53/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
java
Ambito
api

Direzione di ricerca

Start by reading the deploy service REST API contract and the code that handles deployment requests; the issue does not name specific files or tests. Trace how the CLI's module and resource filters reach partial deployment, then identify how equivalent optional parameters could fit the API. Done means API consumers can request selected modules or resources while requests without filters still deploy the full archive.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

The MultiApps Controller supports partial deployment when triggered via cf deploy -m -r through the CLI plugin. However, when the controller is invoked via its REST API — as done by SAP Cloud Transport Management (Cloud TMS) during import operations — there is no documented mechanism to pass module/resource selection parameters. This means Cloud TMS always triggers a full archive deployment.

Expected behavior: The deploy service REST API accepts optional modules and resources filter parameters, allowing API consumers (Cloud TMS, CI/CD tools, custom automation) to trigger partial deployments programmatically — equivalent to the -m/-r flags in the CLI.
Actual behavior: The API deploys the full .mtar archive. No module/resource filter is available. The partial deployment capability is only accessible through the CLI plugin, not through API integration.
Why this matters:

Teams using Cloud TMS for transport governance (audit trail, approval workflows, landscape routing) cannot use partial deployment. They must choose between:

Transport governance via Cloud TMS — but always full deployment
Deployment granularity via cf deploy -m — but bypassing transport governance
Exposing the filter at the API level would allow Cloud TMS (and other tools) to add partial deployment support without changes to the controller's core deployment logic — only the API contract needs to be extended.

Default behavior should remain unchanged: no filter parameters = full deploy, as today.

Your environment
MultiApps Controller version — SAP BTP managed (latest)
MultiApps CF CLI Plugin version — latest
which CF vendor is used — SAP BTP Cloud Foundry
which backing services are used — hana / hdi-shared (HDI container), SAP Cloud Transport Management
Steps to reproduce
Not a bug — feature request. The gap can be observed by:

Configuring a CI/CD pipeline that uploads an .mtar to Cloud TMS
Importing the transport at the target node
Observing that the full MTA is deployed — there is no option to select specific modules

Lingua principale
Java
Stelle
65
Fork
41
Merge medio
1g 12m
PR unite (30g)
7

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di cloudfoundry/multiapps-controller

Tutte le issue di cloudfoundry/multiapps-controller

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.