psa-systems/mokosh-apps
Watch
9
0
Fork
You've already forked mokosh-apps
 0
Code Issues Pull requests 1 Projects Releases 14 Packages Wiki Activity Actions

feat(assets): add/remove UI for asset relationships #419

Merged
Claude-Run merged 1 commit from feat/MAPPS-233-asset-relationships-add-remove into main 2026-07-04 06:12:30 +02:00
Conversation 0 Commits 1 Files changed 1 +258 -9
Claude-Run commented 2026-07-04 06:10:57 +02:00
Member
Copy link

The asset detail Relationships card was read-only: relationships fetched from GET /assets/{id}/relationships rendered as static badge+link rows with no way to create or remove them.

Add an "Add" action on the card that opens a modal (AssetPicker for the related/child asset, Select for the relationship type: Depends On / Hosts / Connected To / Contains) and POSTs to /assets/{id}/relationships, plus a per-row Remove (trash) button that confirms via ConfirmDialog and DELETEs /asset-relationships/{id}. Both refresh the relationships list and the audit log on success. The flow mirrors the MAPPS-231 credentials add/remove pattern, including the MAPPS-357 server-down disabling of the mutate controls.

RemoteRelationship now also deserializes the row id (optional, so a row without one just renders no Remove button) needed to address the delete endpoint.

#MAPPS-233

The asset detail Relationships card was read-only: relationships fetched from GET /assets/{id}/relationships rendered as static badge+link rows with no way to create or remove them. Add an "Add" action on the card that opens a modal (AssetPicker for the related/child asset, Select for the relationship type: Depends On / Hosts / Connected To / Contains) and POSTs to /assets/{id}/relationships, plus a per-row Remove (trash) button that confirms via ConfirmDialog and DELETEs /asset-relationships/{id}. Both refresh the relationships list and the audit log on success. The flow mirrors the MAPPS-231 credentials add/remove pattern, including the MAPPS-357 server-down disabling of the mutate controls. RemoteRelationship now also deserializes the row `id` (optional, so a row without one just renders no Remove button) needed to address the delete endpoint. #MAPPS-233
feat(assets): add/remove UI for asset relationships
All checks were successful
Check / fmt + clippy + tests (pull_request) Successful in 1m27s
Details
Create release / Create release from merged PR (pull_request) Has been skipped
Details
559fdc5251 
The asset detail Relationships card was read-only: relationships fetched from GET /assets/{id}/relationships rendered as static badge+link rows with no way to create or remove them.

Add an "Add" action on the card that opens a modal (AssetPicker for the related/child asset, Select for the relationship type: Depends On / Hosts / Connected To / Contains) and POSTs to /assets/{id}/relationships, plus a per-row Remove (trash) button that confirms via ConfirmDialog and DELETEs /asset-relationships/{id}. Both refresh the relationships list and the audit log on success. The flow mirrors the MAPPS-231 credentials add/remove pattern, including the MAPPS-357 server-down disabling of the mutate controls.

RemoteRelationship now also deserializes the row `id` (optional, so a row without one just renders no Remove button) needed to address the delete endpoint.

#MAPPS-233
Claude-Run deleted branch feat/MAPPS-233-asset-relationships-add-remove 2026-07-04 06:12:30 +02:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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
psa-systems/mokosh-apps!419
No description provided.