schemas update: confirm step (--digest/--confirm) returns ok:true but never persists the change
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 65/100
- Issue 类型
- 缺陷
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- cli, shell
调研方向
Look at the schemas update command implementation, likely in a file like src/commands/schemas/update.rs or similar. The bug is in the confirm step where the digest is used but the change is not persisted. Start by tracing the flow from the --confirm flag, checking the API call made and the response handling. Verify the actual write operation to the CRM. Run the provided reproduction steps to see the issue firsthand.
由索引模型根据 Issue 内容生成。
描述
Version: hubspot 0.14.0 (build 1162, commit unknown)
Command run:
$ PATCH='{"labels":{"singular":"ZZ Push Test","plural":"ZZ Push Tests MANUAL"}}'
$ DIGEST=$(echo "$PATCH" | hubspot schemas update --type 2-253815111 --dry-run | jq -r '.digest')
$ echo "$PATCH" | hubspot schemas update --type 2-253815111 --digest "$DIGEST" --confirm 'zz_push_test'
Expected result: the schema's labels.plural is updated to "ZZ Push Tests MANUAL", matching what the confirm call's own response claims to have applied.
Actual result: the confirm call returns ok: true with a data payload that shows the new value, but the change is never written. Re-fetching immediately after (and repeatedly for 25s afterward) shows the old value unchanged:
$ echo "$PATCH" | hubspot schemas update --type 2-253815111 --digest "$DIGEST" --confirm 'zz_push_test'
{"name":"2-253815111","ok":true,"data":{"labels":{"singular":"ZZ Push Test","plural":"ZZ Push Tests MANUAL"},...}}
$ hubspot schemas get --type 2-253815111 --format json | jq '.data[0].labels'
{"singular":"ZZ Push Test","plural":"ZZ Push Tests"}
Reproduced twice independently (once via a wrapper script, once with the raw commands above in isolation, no other operations in between).
Why this matters: the README's own beta warning recommends using --dry-run before mutations as the safety practice for a tool that can modify live CRM data. This defeats that practice for schemas update specifically - the confirm step that --dry-run leads into silently no-ops while reporting success.
Also noticed while investigating: the dry-run response's apply_command_hint field (e.g. hubspot schemas update 2-253815111 --digest blast-... --confirm 'zz_push_test') omits --file/stdin, which is misleading on its own - the confirm call does require the same JSON body piped again, or it fails with "No schema body provided".
- 主要语言
- 没有语言数据
- 星标
- 7
- 派生
- 2
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
HubSpot/agent-cli 的其他 Issue
-
properties get/list/batch-read appear unable to retrieve sensitive or highly-sensitive properties未关闭
难度 3/5 1-2 天 新手友好度 68/100
-
难度 3/5 1-2 天 新手友好度 65/100
-
难度 4/5 3-5 天 新手友好度 48/100
查看 HubSpot/agent-cli 的全部 Issue
相似的 Issue
-
enhancement help wanted
难度 2/5 1-3 小时 新手友好度 78/100
ecosyste-ms/repos#1215 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 88/100
pop-os/cosmic-comp#2956 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 90/100
维护者通常 1 天内回复
-
GET rooms API returns 500 due to nonexistent Room.is_active attribute可能已有人在做 @Mars-60 今天认领。 未关闭bug
难度 2/5 1-3 小时 新手友好度 84/100
维护者通常 1 天内回复
-
loginWithCustomTokenExchange() fails when an organization is configured可能已有人在做 @awss1i 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 65/100
维护者通常 2 天内回复