RosaAI integration findings: feature requests + update_app field issue #9

New issue

Open

opened 2026-05-13 11:57:16 +00:00 by Robby.Fritzsch · 0 comments

Robby.Fritzsch commented

2026-05-13 11:57:16 +00:00

Member

During the IPCEICIS-8110 MCP integration spike, we evaluated edge-connect-mcp as the CRUD backend for RosaAI's agent tools. Live testing (create/read/update/delete cycle) validated the tool implementations — three of four operations worked correctly. Full analysis is in the deep dive and proposal.

Issue found

update_app with access_ports returns 400:
Calling update_app(org=TMMS, name=mcp-test-nginx, version=1.0.0, access_ports="tcp:80,tcp:443") returns 400: Invalid field specified: CreatedAt.Seconds. The tool implementation looks correct — it uses a Fields list scoped to AppFieldAccessPorts. The error suggests the API treats access_ports (or a related derived field) as internal-use. Unclear whether this is an API-side restriction or a field mapping issue in the SDK.

More broadly: which fields are user-updatable vs internal-use is not documented in the tool descriptions or the EdgeConnect API spec.

Feature requests

These would benefit all ec-mcp consumers, not just RosaAI:

Feature	Priority	Rationale
`list_cloudlets`	High	Any consumer deploying app instances needs to discover available cloudlets. Blocks full CRUD workflow for RosaAI.
`list_flavors` / `list_flavors_for_cloudlet`	High	Needed to select resources for app instances. Same blocker.
Cascade delete flag on `delete_app`	Medium	Common UX need — currently requires manually deleting all instances first.
Test/mock mode (`--mock` or fixture config)	Low	Useful for consumers writing integration tests without a real API.

During the [IPCEICIS-8110 MCP integration spike](https://jira.telekom-mms.com/browse/IPCEICIS-8110), we evaluated edge-connect-mcp as the CRUD backend for RosaAI's agent tools. Live testing (create/read/update/delete cycle) validated the tool implementations — three of four operations worked correctly. Full analysis is in the [deep dive](https://gitlab.devops.telekom.de/ipcei-cis/architecture/ai/iac-llm/-/wikis/topics/mcp-integration/deep-dive_edge-connect-mcp) and [proposal](https://gitlab.devops.telekom.de/ipcei-cis/architecture/ai/iac-llm/-/wikis/topics/mcp-integration/proposal_ec-mcp-tool-replacement). ## Issue found **`update_app` with `access_ports` returns 400:** Calling `update_app(org=TMMS, name=mcp-test-nginx, version=1.0.0, access_ports="tcp:80,tcp:443")` returns `400: Invalid field specified: CreatedAt.Seconds`. The tool implementation looks correct — it uses a `Fields` list scoped to `AppFieldAccessPorts`. The error suggests the API treats `access_ports` (or a related derived field) as internal-use. Unclear whether this is an API-side restriction or a field mapping issue in the SDK. More broadly: which fields are user-updatable vs internal-use is not documented in the tool descriptions or the EdgeConnect API spec. ## Feature requests These would benefit all ec-mcp consumers, not just RosaAI: | Feature | Priority | Rationale | |---------|----------|-----------| | `list_cloudlets` | High | Any consumer deploying app instances needs to discover available cloudlets. Blocks full CRUD workflow for RosaAI. | | `list_flavors` / `list_flavors_for_cloudlet` | High | Needed to select resources for app instances. Same blocker. | | Cascade delete flag on `delete_app` | Medium | Common UX need — currently requires manually deleting all instances first. | | Test/mock mode (`--mock` or fixture config) | Low | Useful for consumers writing integration tests without a real API. |

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

DevFW-CICD/edge-connect-mcp#9

No description provided.

Rows
Columns