Description:
Problem
There's currently no CLI command to inspect a repo's AI Code Review (AICR)
settings. Users can view AICR results on a PR (get pr:insight), but not
whether/how AICR is configured for a repo (enabled/disabled, recursive
inheritance from parent scopes, rule configuration, etc.).
Proposed command
harness get aicr_settings --repo <repo> (naming TBD — could also be
get code_review_settings or nested under get repo:aicr_settings,
mirroring the existing pr:insight sub-resource pattern).
API endpoint
```
GET /gateway/aicr/api/v1/settings?repo_path={repo_path}&recursive=true
```
repo_path — URL-encoded repo path (e.g. l7B_kbSEQD2wjrM7PShm5w/PROD/Harness_Commons/harness-core)recursive — when true, includes settings inherited from parent scopes (account/org/project)
Scope questions to resolve before implementing
- Should this only support
get, or also update/set for changing AICR
settings (title says "changing the setting" — need to confirm whether
there's a corresponding PUT/PATCH endpoint for writes)? - Where should
repo_path come from — derived from the existing --repo
identifier resolution the rest of the code module uses, or a raw flag? - Output shape: what fields does the settings response actually contain?
Need a sample response to design the noun's fields/columns.
Description:
Problem
There's currently no CLI command to inspect a repo's AI Code Review (AICR)
settings. Users can view AICR results on a PR (
get pr:insight), but notwhether/how AICR is configured for a repo (enabled/disabled, recursive
inheritance from parent scopes, rule configuration, etc.).
Proposed command
harness get aicr_settings --repo <repo>(naming TBD — could also beget code_review_settingsor nested underget repo:aicr_settings,mirroring the existing
pr:insightsub-resource pattern).API endpoint
```
GET /gateway/aicr/api/v1/settings?repo_path={repo_path}&recursive=true
```
repo_path— URL-encoded repo path (e.g.l7B_kbSEQD2wjrM7PShm5w/PROD/Harness_Commons/harness-core)recursive— whentrue, includes settings inherited from parent scopes (account/org/project)Scope questions to resolve before implementing
get, or alsoupdate/setfor changing AICRsettings (title says "changing the setting" — need to confirm whether
there's a corresponding
PUT/PATCHendpoint for writes)?repo_pathcome from — derived from the existing--repoidentifier resolution the rest of the
codemodule uses, or a raw flag?Need a sample response to design the noun's fields/columns.