You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[upstream-adapt] Audit Drive sharing for folders and files #163
Drive already exposes file search/listing and permission CRUD, but it has no recursive sharing-audit result model. The requested outcome is novel and no local prior-rejection record matches it.
The implementation contract is not yet durable because "who can access," "external sharing," and "anomalies" are undefined for inherited permissions, domains, groups, link sharing, shared drives, and inaccessible descendants. The maintainer also needs to decide whether this is a raw permission inventory or an opinionated security assessment.
Recommendation: retain needs-triage until the audit semantics, traversal boundary, and minimum machine-readable fields are chosen.
The Drive surface can list files and manage or inspect permissions on one resource, including shared-drive resources, but it has no recursive sharing-audit model or report. Closed-issue, merged-PR, source, and prior-rejection searches found no duplicate or already-implemented equivalent.
The request is not yet a testable contract: “who can access,” “external,” and “anomaly” need definitions for inherited permissions, groups, domains, link sharing, shared drives, inaccessible descendants, and permission expansion that gog cannot resolve locally. A maintainer must also choose whether the first product is a factual permission inventory or an opinionated security assessment, plus the traversal boundary and minimum machine-readable fields.
Recommendation: retain needs-triage until those audit semantics are selected.
Drive currently supports folder listing, search, individual-resource metadata, shared-drive-aware operations, and permission inspection and mutation. It does not recursively traverse a file tree or produce a sharing-audit result that identifies effective access, external exposure, or anomalies.
Searches of the source snapshot, closed issues, and merged pull requests found no equivalent audit workflow, and no prior-rejection record exists.
The requested result is not yet a testable contract. A maintainer must define whether this is a factual permission inventory or an opinionated security assessment, what “external” and “anomaly” mean, the traversal boundary, the minimum machine-readable fields, and the treatment of inherited permissions, groups, domains, link sharing, shared drives, and inaccessible descendants.
Recommendation: retain needs-triage until those audit semantics and boundaries are selected.
Drive supports listing and searching files, shared-drive-aware operations, and inspecting or mutating permissions on one resource. It does not recursively traverse a file tree or produce a sharing-audit result for effective access, external exposure, or anomalies. No equivalent appears in the closed-issue or merged-PR snapshots, and no prior-rejection record exists.
The requested report is not yet a testable contract. A maintainer must decide whether the first product is a factual permission inventory or an opinionated security assessment, define “external” and “anomaly,” choose the traversal boundary and minimum machine-readable fields, and specify treatment of inherited permissions, groups, domains, link sharing, shared drives, and inaccessible descendants.
Recommendation: retain needs-triage until those audit semantics and boundaries are selected.
Drive supports listing and searching files, shared-drive-aware operations, and inspecting or mutating permissions on one resource. It does not recursively traverse a file tree or produce a sharing-audit result for effective access, external exposure, or anomalies. No equivalent appears in the closed-issue or merged-PR snapshots, and there is no prior-rejection record.
The requested report is not yet a testable contract. A maintainer must choose whether the first product is a factual permission inventory or an opinionated security assessment, define “external” and “anomaly,” select the traversal boundary and minimum machine-readable fields, and specify treatment of inherited permissions, groups, domains, link sharing, shared drives, and inaccessible descendants. Retain needs-triage until those audit semantics and boundaries are selected.
Drive supports listing and searching files, shared-drive-aware operations, and inspecting or mutating permissions on one resource. It does not recursively traverse a file tree or produce a sharing-audit result for effective access, external exposure, or anomalies. The supplied source and historical snapshots contain no equivalent implementation, and there is no prior-rejection record.
The requested report is not yet a testable product contract. A maintainer must choose whether the first product is a factual permission inventory or an opinionated security assessment, define “external” and “anomaly,” select the traversal boundary and minimum machine-readable fields, and specify treatment of inherited permissions, groups, domains, link sharing, shared drives, and inaccessible descendants. Retain needs-triage until those audit semantics and boundaries are selected.
Drive supports listing and searching files, shared-drive-aware operations, and inspecting permissions on one resource. It does not recursively traverse a file tree or produce a sharing-audit result for effective access, external exposure, or anomalies. The source and historical snapshots contain no equivalent implementation, and there is no prior-rejection record.
The requested report is not yet a testable product contract. A maintainer must choose whether the first product is a factual permission inventory or an opinionated security assessment, define “external” and “anomaly,” select the traversal boundary and minimum machine-readable fields, and specify treatment of inherited permissions, groups, domains, link sharing, shared drives, and inaccessible descendants. Retain needs-triage until those audit semantics and boundaries are selected.
Drive supports listing and searching files, shared-drive-aware operations, and permission inspection on one resource. It does not recursively traverse a file tree or produce a sharing-audit result for effective access, external exposure, or anomalies. The current source and supplied historical snapshots contain no equivalent implementation, and there is no prior-rejection record.
The requested report is not yet a testable product contract. A maintainer must choose whether the first product is a factual permission inventory or an opinionated security assessment, define “external” and “anomaly,” select the traversal boundary and minimum machine-readable fields, and specify treatment of inherited permissions, groups, domains, link sharing, shared drives, and inaccessible descendants. Retain needs-triage until those audit semantics and boundaries are selected.
Drive supports listing and searching files, shared-drive-aware operations, and permission inspection on one resource. It does not recursively traverse a file tree or produce a sharing-audit result for effective access, external exposure, or anomalies. Searches across the Drive command and client surfaces and the supplied issue and PR histories found no equivalent implementation or duplicate; no prior-rejection record exists.
The report is not yet a testable product contract. A maintainer must choose whether the first product is a factual permission inventory or an opinionated security assessment, define “external” and “anomaly,” select the traversal boundary and minimum machine-readable fields, and specify treatment of inherited permissions, groups, domains, link sharing, shared drives, and inaccessible descendants. Retain needs-triage until those audit semantics and boundaries are selected.
Drive supports listing and searching files, shared-drive-aware operations, and permission inspection on one resource. It does not recursively traverse a tree or produce a sharing-audit result for effective access, external exposure, or anomalies. Searches of the Drive command and client concepts and the supplied histories found no equivalent implementation or duplicate, and there is no prior-rejection record.
The report is not yet a testable product contract. A maintainer must choose whether the first product is a factual permission inventory or an opinionated security assessment; define “external” and “anomaly”; select the traversal boundary and machine-readable fields; and specify treatment of inherited permissions, groups, domains, link sharing, shared drives, and inaccessible descendants. Retain needs-triage until those semantics and boundaries are selected.
Drive supports listing and searching files, shared-drive-aware operations, and permission inspection on one resource. It does not recursively traverse a tree or produce a sharing-audit result for effective access, external exposure, or anomalies. Searches of the Drive command surface and supplied histories found no equivalent implementation or duplicate, and there is no prior-rejection record.
The report is not yet a testable product contract. A maintainer must choose whether the first product is a factual permission inventory or an opinionated security assessment; define “external” and “anomaly”; select the traversal boundary and machine-readable fields; and specify treatment of inherited permissions, groups, domains, link sharing, shared drives, and inaccessible descendants. Retain needs-triage until those semantics and boundaries are selected.
Drive supports listing and searching files, shared-drive-aware operations, and permission inspection for one resource. It does not recursively traverse a tree or produce a sharing-audit result for effective access, external exposure, or anomalies. Searches of the Drive command and permission concepts and the supplied closed-issue and merged-PR histories found no equivalent implementation or duplicate; no prior-rejection record exists.
The requested report is not yet a testable product contract. A maintainer must choose whether the first product is a factual permission inventory or an opinionated security assessment; define “external” and “anomaly”; select traversal boundaries and machine-readable fields; and specify treatment of inherited permissions, groups, domains, link sharing, shared drives, and inaccessible descendants. Keep this in needs-triage until those semantics are selected.
Drive supports listing and searching files, shared-drive-aware operations, and permission inspection for one resource. It does not recursively traverse a tree or produce a sharing-audit result for effective access, external exposure, or anomalies. Concept searches of the Drive surface and supplied histories found no equivalent implementation or duplicate, and there is no prior-rejection record.
The requested report is not yet a testable product contract. A maintainer must choose whether the first product is a factual permission inventory or an opinionated security assessment; define “external” and “anomaly”; select traversal boundaries and machine-readable fields; and specify treatment of inherited permissions, groups, domains, link sharing, shared drives, and inaccessible descendants. Retain needs-triage until those audit semantics are selected.
Category: enhancement Summary: Operators can report who can access a Drive folder/file tree (permissions, external sharing, anomalies) in script-friendly output.
Current behavior:
Fork lacks this upstream-adapt capability (or only partial primitives exist). Prior triage notes on this issue document the current surface.
Desired behavior:
Operators can report who can access a Drive folder/file tree (permissions, external sharing, anomalies) in script-friendly output.
Key interfaces:
Existing gog CLI command surface and auth/safety controls
Google API surface named in the issue outcome
Script-friendly machine-readable output consistent with sibling commands
Acceptance criteria:
Outcome in the issue body is met under this fork’s architecture (adapt, do not cherry-pick upstream patches)
Behavior is covered by tests or documented manual verification
Safety/auth constraints match the rest of gog
Out of scope:
Copying upstream implementation wholesale
Unrelated Google services
Why not delegable
Product priority and contract semantics are still open (what ships first, audit/lifecycle meaning, and whether this fork needs the capability at all). An agent should not invent those decisions. Once Jeremy ranks or rejects this upstream-adapt item, retarget to ready-for-agent or wontfix.
Prior triage notes remain the technical baseline; this comment only advances state out of needs-triage.
Closing as obsolete (GitHub sweep 2026-10-12). This [upstream-adapt] request asked to port an upstream steipete/gogcli CLI feature into our gog CLI. That CLI was retired in 91336b7 (#269); main builds only gog-mcp, so the command surface this request targets no longer exists. gog-mcp's pinned API catalog (internal/googlecatalog/manifest.json) already exposes the underlying Google method(s) (drive.permissions.list, drive.files.list) through --discovery=compact --api-catalog, subject to grants. New needs on the MCP side are filed as MCP-scoped issues (see #271, #273, #274, #278).
Activity
itsjeremyjohnson commentedon Aug 12, 2026
Triage Notes
Drive already exposes file search/listing and permission CRUD, but it has no recursive sharing-audit result model. The requested outcome is novel and no local prior-rejection record matches it.
The implementation contract is not yet durable because "who can access," "external sharing," and "anomalies" are undefined for inherited permissions, domains, groups, link sharing, shared drives, and inaccessible descendants. The maintainer also needs to decide whether this is a raw permission inventory or an opinionated security assessment.
Recommendation: retain
needs-triageuntil the audit semantics, traversal boundary, and minimum machine-readable fields are chosen.itsjeremyjohnson commentedon Aug 13, 2026
Triage Notes
The Drive surface can list files and manage or inspect permissions on one resource, including shared-drive resources, but it has no recursive sharing-audit model or report. Closed-issue, merged-PR, source, and prior-rejection searches found no duplicate or already-implemented equivalent.
The request is not yet a testable contract: “who can access,” “external,” and “anomaly” need definitions for inherited permissions, groups, domains, link sharing, shared drives, inaccessible descendants, and permission expansion that gog cannot resolve locally. A maintainer must also choose whether the first product is a factual permission inventory or an opinionated security assessment, plus the traversal boundary and minimum machine-readable fields.
Recommendation: retain
needs-triageuntil those audit semantics are selected.itsjeremyjohnson commentedon Aug 14, 2026
Triage Notes
Drive currently supports folder listing, search, individual-resource metadata, shared-drive-aware operations, and permission inspection and mutation. It does not recursively traverse a file tree or produce a sharing-audit result that identifies effective access, external exposure, or anomalies.
Searches of the source snapshot, closed issues, and merged pull requests found no equivalent audit workflow, and no prior-rejection record exists.
The requested result is not yet a testable contract. A maintainer must define whether this is a factual permission inventory or an opinionated security assessment, what “external” and “anomaly” mean, the traversal boundary, the minimum machine-readable fields, and the treatment of inherited permissions, groups, domains, link sharing, shared drives, and inaccessible descendants.
Recommendation: retain
needs-triageuntil those audit semantics and boundaries are selected.itsjeremyjohnson commentedon Aug 15, 2026
Triage Notes
Drive supports listing and searching files, shared-drive-aware operations, and inspecting or mutating permissions on one resource. It does not recursively traverse a file tree or produce a sharing-audit result for effective access, external exposure, or anomalies. No equivalent appears in the closed-issue or merged-PR snapshots, and no prior-rejection record exists.
The requested report is not yet a testable contract. A maintainer must decide whether the first product is a factual permission inventory or an opinionated security assessment, define “external” and “anomaly,” choose the traversal boundary and minimum machine-readable fields, and specify treatment of inherited permissions, groups, domains, link sharing, shared drives, and inaccessible descendants.
Recommendation: retain
needs-triageuntil those audit semantics and boundaries are selected.itsjeremyjohnson commentedon Aug 16, 2026
Triage Notes
Drive supports listing and searching files, shared-drive-aware operations, and inspecting or mutating permissions on one resource. It does not recursively traverse a file tree or produce a sharing-audit result for effective access, external exposure, or anomalies. No equivalent appears in the closed-issue or merged-PR snapshots, and there is no prior-rejection record.
The requested report is not yet a testable contract. A maintainer must choose whether the first product is a factual permission inventory or an opinionated security assessment, define “external” and “anomaly,” select the traversal boundary and minimum machine-readable fields, and specify treatment of inherited permissions, groups, domains, link sharing, shared drives, and inaccessible descendants. Retain
needs-triageuntil those audit semantics and boundaries are selected.itsjeremyjohnson commentedon Aug 17, 2026
Triage Notes
Drive supports listing and searching files, shared-drive-aware operations, and inspecting or mutating permissions on one resource. It does not recursively traverse a file tree or produce a sharing-audit result for effective access, external exposure, or anomalies. The supplied source and historical snapshots contain no equivalent implementation, and there is no prior-rejection record.
The requested report is not yet a testable product contract. A maintainer must choose whether the first product is a factual permission inventory or an opinionated security assessment, define “external” and “anomaly,” select the traversal boundary and minimum machine-readable fields, and specify treatment of inherited permissions, groups, domains, link sharing, shared drives, and inaccessible descendants. Retain
needs-triageuntil those audit semantics and boundaries are selected.itsjeremyjohnson commentedon Aug 18, 2026
Triage Notes
Drive supports listing and searching files, shared-drive-aware operations, and inspecting permissions on one resource. It does not recursively traverse a file tree or produce a sharing-audit result for effective access, external exposure, or anomalies. The source and historical snapshots contain no equivalent implementation, and there is no prior-rejection record.
The requested report is not yet a testable product contract. A maintainer must choose whether the first product is a factual permission inventory or an opinionated security assessment, define “external” and “anomaly,” select the traversal boundary and minimum machine-readable fields, and specify treatment of inherited permissions, groups, domains, link sharing, shared drives, and inaccessible descendants. Retain
needs-triageuntil those audit semantics and boundaries are selected.itsjeremyjohnson commentedon Aug 20, 2026
Triage Notes
Drive supports listing and searching files, shared-drive-aware operations, and permission inspection on one resource. It does not recursively traverse a file tree or produce a sharing-audit result for effective access, external exposure, or anomalies. The current source and supplied historical snapshots contain no equivalent implementation, and there is no prior-rejection record.
The requested report is not yet a testable product contract. A maintainer must choose whether the first product is a factual permission inventory or an opinionated security assessment, define “external” and “anomaly,” select the traversal boundary and minimum machine-readable fields, and specify treatment of inherited permissions, groups, domains, link sharing, shared drives, and inaccessible descendants. Retain
needs-triageuntil those audit semantics and boundaries are selected.itsjeremyjohnson commentedon Aug 21, 2026
Triage Notes
Drive supports listing and searching files, shared-drive-aware operations, and permission inspection on one resource. It does not recursively traverse a file tree or produce a sharing-audit result for effective access, external exposure, or anomalies. Searches across the Drive command and client surfaces and the supplied issue and PR histories found no equivalent implementation or duplicate; no prior-rejection record exists.
The report is not yet a testable product contract. A maintainer must choose whether the first product is a factual permission inventory or an opinionated security assessment, define “external” and “anomaly,” select the traversal boundary and minimum machine-readable fields, and specify treatment of inherited permissions, groups, domains, link sharing, shared drives, and inaccessible descendants. Retain
needs-triageuntil those audit semantics and boundaries are selected.itsjeremyjohnson commentedon Aug 23, 2026
Triage Notes
Drive supports listing and searching files, shared-drive-aware operations, and permission inspection on one resource. It does not recursively traverse a tree or produce a sharing-audit result for effective access, external exposure, or anomalies. Searches of the Drive command and client concepts and the supplied histories found no equivalent implementation or duplicate, and there is no prior-rejection record.
The report is not yet a testable product contract. A maintainer must choose whether the first product is a factual permission inventory or an opinionated security assessment; define “external” and “anomaly”; select the traversal boundary and machine-readable fields; and specify treatment of inherited permissions, groups, domains, link sharing, shared drives, and inaccessible descendants. Retain
needs-triageuntil those semantics and boundaries are selected.itsjeremyjohnson commentedon Aug 23, 2026
Triage Notes
Drive supports listing and searching files, shared-drive-aware operations, and permission inspection on one resource. It does not recursively traverse a tree or produce a sharing-audit result for effective access, external exposure, or anomalies. Searches of the Drive command surface and supplied histories found no equivalent implementation or duplicate, and there is no prior-rejection record.
The report is not yet a testable product contract. A maintainer must choose whether the first product is a factual permission inventory or an opinionated security assessment; define “external” and “anomaly”; select the traversal boundary and machine-readable fields; and specify treatment of inherited permissions, groups, domains, link sharing, shared drives, and inaccessible descendants. Retain
needs-triageuntil those semantics and boundaries are selected.itsjeremyjohnson commentedon Aug 24, 2026
Triage Notes
Drive supports listing and searching files, shared-drive-aware operations, and permission inspection for one resource. It does not recursively traverse a tree or produce a sharing-audit result for effective access, external exposure, or anomalies. Searches of the Drive command and permission concepts and the supplied closed-issue and merged-PR histories found no equivalent implementation or duplicate; no prior-rejection record exists.
The requested report is not yet a testable product contract. A maintainer must choose whether the first product is a factual permission inventory or an opinionated security assessment; define “external” and “anomaly”; select traversal boundaries and machine-readable fields; and specify treatment of inherited permissions, groups, domains, link sharing, shared drives, and inaccessible descendants. Keep this in
needs-triageuntil those semantics are selected.itsjeremyjohnson commentedon Aug 25, 2026
Triage Notes
Drive supports listing and searching files, shared-drive-aware operations, and permission inspection for one resource. It does not recursively traverse a tree or produce a sharing-audit result for effective access, external exposure, or anomalies. Concept searches of the Drive surface and supplied histories found no equivalent implementation or duplicate, and there is no prior-rejection record.
The requested report is not yet a testable product contract. A maintainer must choose whether the first product is a factual permission inventory or an opinionated security assessment; define “external” and “anomaly”; select traversal boundaries and machine-readable fields; and specify treatment of inherited permissions, groups, domains, link sharing, shared drives, and inaccessible descendants. Retain
needs-triageuntil those audit semantics are selected.itsjeremyjohnson commentedon Sep 15, 2026
Agent Brief
Category: enhancement
Summary: Operators can report who can access a Drive folder/file tree (permissions, external sharing, anomalies) in script-friendly output.
Current behavior:
Fork lacks this upstream-adapt capability (or only partial primitives exist). Prior triage notes on this issue document the current surface.
Desired behavior:
Operators can report who can access a Drive folder/file tree (permissions, external sharing, anomalies) in script-friendly output.
Key interfaces:
Acceptance criteria:
Out of scope:
Why not delegable
Product priority and contract semantics are still open (what ships first, audit/lifecycle meaning, and whether this fork needs the capability at all). An agent should not invent those decisions. Once Jeremy ranks or rejects this upstream-adapt item, retarget to
ready-for-agentorwontfix.Prior triage notes remain the technical baseline; this comment only advances state out of
needs-triage.itsjeremyjohnson commentedon Oct 12, 2026
Closing as obsolete (GitHub sweep 2026-10-12). This [upstream-adapt] request asked to port an upstream steipete/gogcli CLI feature into our
gogCLI. That CLI was retired in 91336b7 (#269);mainbuilds onlygog-mcp, so the command surface this request targets no longer exists.gog-mcp's pinned API catalog (internal/googlecatalog/manifest.json) already exposes the underlying Google method(s) (drive.permissions.list, drive.files.list) through--discovery=compact --api-catalog, subject to grants. New needs on the MCP side are filed as MCP-scoped issues (see #271, #273, #274, #278).