properties get/list/batch-read appear unable to retrieve sensitive or highly-sensitive properties
还没有人认领这个 Issue。
评估
调研方向
Start with the implementations of properties get, properties list, and properties batch-read, then compare their requests with the documented HubSpot Properties API behavior described here. Verify how each command handles the dataSensitivity query parameter and inspect existing command tests if present. Done means sensitive and highly sensitive properties are reachable through the read paths, with the intended default and filtering behavior covered.
由索引模型根据 Issue 内容生成。
描述
HubSpot's Properties API filters by dataSensitivity tier on read: GET /crm/v3/properties/{type} and GET /crm/v3/properties/{type}/{name} return only non-sensitive properties by default, and need a ?dataSensitivity=sensitive or ?dataSensitivity=highly_sensitive query parameter to return properties at that tier. Each value looks to be an exact match rather than cumulative, it seems getting every property regardless of tier needs three separate calls (no parameter, ?dataSensitivity=sensitive, ?dataSensitivity=highly_sensitive) merged together.
As far as we could find, none of properties get, properties list, or properties batch-read expose a flag for this parameter, and we couldn't locate a generic raw-request/escape-hatch command elsewhere in the CLI either (checked the full top-level hubspot --help command surface). So it looks like a property with a dataSensitivity of sensitive or highly_sensitive may not be reachable through any of the CLI's read paths, even though it exists and is correctly configured (visible in the HubSpot UI, retrievable via the raw API with the right parameter). Happy to be pointed at something we missed if this is already supported somewhere.
Reproduction:
hubspot properties get --type contacts <a property with dataSensitivity set>
→ {"ok":false,"error":{"status":404,"message":"No property named '<name>' exists."}}
hubspot properties list --type contacts --format json | grep <name>
→ (no output, property appears absent from the list)
printf '<name>' | hubspot properties batch-read --type contacts
→ No results.
All three behave the same way for a property that HubSpot's own Settings UI shows as correctly configured.
Possible fix: our preference would be for list/batch-read to merge all three tiers by default, since a property being invisible by default based on its sensitivity seems like a surprising gotcha to hit rather than something a caller would need to opt into avoiding. A --data-sensitivity <sensitive|highly_sensitive> flag would still be useful on top of that for anyone wanting to filter to a specific tier, but shouldn't be required just to see everything.
- 主要语言
- 没有语言数据
- 星标
- 7
- 派生
- 2
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
HubSpot/agent-cli 的其他 Issue
-
难度 3/5 1-2 天 新手友好度 65/100
-
难度 3/5 1-2 天 新手友好度 65/100
-
难度 4/5 3-5 天 新手友好度 48/100
查看 HubSpot/agent-cli 的全部 Issue
相似的 Issue
-
area/linq bug package/core triage
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
bug engine
难度 2/5 1-3 小时 新手友好度 86/100
frostney/GocciaScript#1746 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
omegaup/omegaup#10353 · 1 条评论 ·
维护者通常 5 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
EmbarkStudios/cargo-deny#910 ·