docs(PYEGERIA_ISSUES): ISSUE-84 live-verified by dwolfson-1b/trellis - #339
Merged
Conversation
contentStatus: DRAFT inside properties on NewElementRequestBody confirmed working end-to-end against a live Egeria server (quickstart-egeria-main, once recovered from an unrelated Postgres pool exhaustion): creates without error, round-trips correctly on read-back, elementHeader.status stays ACTIVE as expected (different axis). BlueprintMaterializer upgraded to use it; ComponentMaterializer's identical gap tracked separately, still open on the trellis side. Signed-off-by: Dan Wolfson <dan.wolfson@pdr-associates.com>
…rification dwolfson-1b/trellis confirmed the real-application-path verification with a concrete guid, independently queried back to confirm contentStatus persisted as DRAFT. 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
Follow-up to #338 (merged) — records live verification of the ISSUE-84 fix against a real Egeria server.
trellis/Resource Explorer confirmed
contentStatus: "DRAFT"insidepropertiesonNewElementRequestBodyworks exactly as the fix describes: creates without error, round-trips correctly on read-back (properties.contentStatus == "DRAFT"), no separate request-body class needed. Verified twice — once as a standalone probe, once through Resource Explorer's actual application path (accepted a real candidate blueprint end-to-end via the Curate UI's API).elementHeader.statusstaysACTIVEregardless, as expected (a different axis, matches the fix's framing).BlueprintMaterializer.materialize_blueprint_elementhas been upgraded on the trellis side to sendcontentStatus: "DRAFT", replacing its ACTIVE-only workaround.ComponentMaterializer's identical gap is still open, tracked separately there.Docs-only change — no code touched.
🤖 Generated with Claude Code