[CXH-2017] - Fix user_type description to match Retool API enum

[sergiocorral-conductorone]

Summary

• Fixes the user_type field description in the account-creation provisioning schema
• The old description listed "endUser" as a valid value, but the Retool API rejects it with HTTP 400
• Updated to reflect the actual accepted values: default, mobile, embed

Fixes CXH-2017

🤖 Generated with Claude Code

[linear-code]

CXH-2017

[github-actions]

Connector PR Review: [CXH-2017] - Fix user_type description to match Retool API enum

Blocking Issues: 0 | Suggestions: 1 | Threads Resolved: 0
Criteria: Criteria status: loaded .claude/skills/ci-review.md from trusted base 0a4c8c6fc8e0.
Review mode: full
View review run

Review Summary
Scanned the full PR diff for security and correctness. This change corrects the user_type provisioning-schema description (removing the invalid "endUser" value), aligns the README note, and adds an allowlist (validUserTypes) that validates user_type in CreateAccount before the API call. The validation is consistent with the docs — the empty string is permitted and defers to the Retool default via the omitempty request field. No new security or correctness issues found.

Security Issues
None found.

Correctness Issues
None found.

Suggestions

• pkg/connector/users.go:138 — The new validUserTypes validation is untested; there is no _test.go in pkg/connector. Consider a small table-driven test covering valid values, empty, and an invalid value to lock in this behavior.

Prompt for AI agents

Verify each finding against the current code and only fix it if needed.

Suggestions:

In pkg/connector/users.go:
- Around line 137-140: The new user_type allowlist validation in CreateAccount has no
  test coverage (there is currently no _test.go in pkg/connector). Add a table-driven
  test that exercises CreateAccount user_type validation for default/mobile/embed
  (accepted), empty string (accepted, defers to API default), and an invalid value such
  as endUser (rejected with codes.InvalidArgument). This locks in the enum contract
  described in the connector.go schema and README.

[github-actions]

No blocking issues found.

[github-actions]

No blocking issues found.