docs(PYEGERIA_ISSUES): log ISSUE-85 -- no create endpoint for SolutionPort, confirmed Egeria-side gap - #340
Merged
Conversation
…nPort, confirmed Egeria-side gap dwolfson-1b/trellis confirmed via live OpenAPI spec inspection (not just .http ground truth) -- 30 POST paths contain "port", all attach/detach, zero creation endpoints. Nothing for pyegeria to build until Egeria adds a real create-port endpoint server-side; follow-on work outlined for when it does. Signed-off-by: Dan Wolfson <dan.wolfson@pdr-associates.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Docs-only. Logs a confirmed Egeria-side gap found by trellis/Resource Explorer while designing a
PortMaterializer: there is no REST endpoint anywhere to create aSolutionPortelement — only attach (to a component), detach, and port-delegation relationships are exposed.Confirmed at every layer:
pyegeria/omvs/solution_architect.py: onlylink_solution_component_port/link_solution_port_delegation(+ detach). Nocreate_solution_port.Egeria-api-solution-architect.http: noPOST .../solution-portscreate path.Link Solution Component Port/Link Solution Port Delegation. NoCreate Solution Port.pyegeria/models/models.py: noSolutionPortPropertiesmodel at all.Not a stale-
.http-file false alarm this time (unlike a similar-looking case in the multi-link audit) —dwolfson-1b/trellis fetched the live OpenAPI spec directly (GET /v3/api-docs, 2.39MB) and searched every path containing "port": 30 POST paths matched, all attach/detach, zero creation endpoints. Confirms the.httpground truth exactly.Nothing to fix in pyegeria until Egeria adds a real create-port endpoint server-side. The entry outlines the follow-on work for when it does (mirrors the
create_solution_blueprint/create_solution_componentpattern from ISSUE-84).🤖 Generated with Claude Code