properties get/list/batch-read appear unable to retrieve sensitive or highly-sensitive properties

Offen
  • Stimmt etwas nicht?
#9 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
68/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Bereich
api, cli

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
Keine Sprachdaten
Sterne
7
Forks
2
Keine gemergten PRs in 30 T.

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus HubSpot/agent-cli

Alle Issues in HubSpot/agent-cli

Ähnliche Issues

Weitere Issues zu Backend & API Design

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.