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

未关闭
#1,945 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
53/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
java
领域
api

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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

主要语言
Java
星标
65
派生
41
平均合并
1 天 12 分钟
30 天内合并 PR
7

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

cloudfoundry/multiapps-controller 的其他 Issue

查看 cloudfoundry/multiapps-controller 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。