Skip to content

Namespace admin APIs under x-speakeasy-group: admin#124

Closed
travis-hoover-glean wants to merge 2 commits into
mainfrom
admin-speakeasy-group
Closed

Namespace admin APIs under x-speakeasy-group: admin#124
travis-hoover-glean wants to merge 2 commits into
mainfrom
admin-speakeasy-group

Conversation

@travis-hoover-glean

Copy link
Copy Markdown
Contributor

Summary

Moves the admin/governance and datasource admin endpoints out of the client.* namespace and into a dedicated admin.* namespace in overlays/admin-modifications-overlay.yaml, so they're accessed as glean.admin.governance..., glean.admin.datasources..., etc.

Groupings

  • admin.governance.data.policies — retrieve, update, list, create, download
  • admin.governance.data.reports — create, download, status
  • admin.governance.data.findings.exports — create, list, download, delete (newly grouped)
  • admin.governance.documents.visibilityoverrides — list, create
  • admin.datasources — getConfiguration, updateConfiguration, getCredentialStatus, rotateCredentials (newly grouped)

Notes

  • The governance endpoints previously sat under client.governance.*; this just swaps the client. prefix for admin..
  • The findings-exports and datasource config/credential paths existed in admin_rest.yaml but were not previously grouped by the overlay — they're now included so all admin APIs share the admin.* namespace.
  • Datasource config + credential operations are grouped flat under admin.datasources. Open to nesting (e.g. admin.datasources.credentials.rotate) if preferred.

Move governance and datasource admin endpoints out of the client.*
namespace and into a dedicated admin.* namespace so they are accessed
as glean.admin.governance.*, glean.admin.datasources.*, etc.

- governance data policies/reports/findings + document visibility overrides
  now live under admin.governance.*
- datasource config/credential endpoints now grouped under admin.datasources
# Conflicts:
#	overlays/admin-modifications-overlay.yaml
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant