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

Aberta
#1,945 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
53/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
java
Domínio
api

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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

Linguagem predominante
Java
Estrelas
65
Forks
41
Merge médio
1d 12min
PRs com merge (30d)
7

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de cloudfoundry/multiapps-controller

Todas as issues de cloudfoundry/multiapps-controller

Issues semelhantes

Mais issues de Java

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.