Go ui_api: add `PUT /v1/environments/:env/ds/nodes/:id` and `DELETE /v1/environments/:env/ds/nodes/:id`
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 52/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- go
- Domain
- api, backend-api-design
Research direction
Start by locating the existing Go ui_api POST /v1/environments/:env/ds/nodes implementation and the ds resource shown by cio schema ds. Compare its behavior with the legacy update and bulk-delete routes, then add the per-node update and delete surface and ensure the schema describes the full lifecycle.
Written by the indexing model from the issue text.
Description
As of 2026-05-14, the Go ui_api now supports POST /v1/environments/:env/ds/nodes for design-studio node creation (huge unlock — thank you). But for per-node updates and deletes, agents still have to fall back to:
PATCH /design-studio/api/workspaces/:ws/nodes/:idon the legacy Design Studio surface for updates, orPOST /v1/environments/:env/ds/node_actions/bulk_deletewith a single-elementnode_idsarray for deletes.
Both work (the legacy surface now accepts service-account JWTs, which it didn't before), but the surface split is awkward — the create returns from the Go ui_api, then you switch hosts/paths to mutate the same resource.
Suggested
Add PUT /v1/environments/:env/ds/nodes/:id (or PATCH) and DELETE /v1/environments/:env/ds/nodes/:id to the Go ui_api so a node's full CRUD lives on one surface.
Why it matters
Today's split makes the cio agent skill more confusing (the ds resource only shows create on its schema; agents have to learn the legacy path separately). Consolidating would let cio schema ds describe the full lifecycle.
- Dominant language
- Go
- Stars
- 5
- Forks
- 1
- Avg merge
- 22m
- Merged PRs (30d)
- 4
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from customerio/cli
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
customerio/cli#63 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
customerio/cli#22 ·
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
linonetwo/cpa-session-archive#25 ·
Maintainers usually reply within 1 day
-
area/testing kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
agent-butler-finding bug
Difficulty 1/5 Under an hour Newbie friendliness 94/100
jordansmall/spindrift#4367 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day