Skip to content

Update admin API client to match latest Amp Admin API spec#50

Open
fordN wants to merge 6 commits intomainfrom
ford/update-admin-api
Open

Update admin API client to match latest Amp Admin API spec#50
fordN wants to merge 6 commits intomainfrom
ford/update-admin-api

Conversation

@fordN
Copy link
Copy Markdown
Contributor

@fordN fordN commented Apr 8, 2026

Summary

  • Sync admin API client with latest server spec (17 new endpoints)
  • Add RevisionsClient for physical table revision management (list, create, activate, prune, truncate, restore)
  • Add job lifecycle endpoints: create(), get_events(), get_progress(), delete_by_status()
  • Add dataset endpoints: list_jobs(), restore(), restore_table(), delete_version()
  • Replace SchemaClient.get_output_schema() with analyze() (supports dependencies, tables, functions)
  • Update deploy params: retry_strategy, verify, worker_id
  • Add CI workflow for spec-drift detection
  • Update API reference and admin client guide docs

Breaking Changes

  • jobs.stop(): POST -> PUT
  • jobs.delete_many() replaced by delete_by_status(status)
  • datasets.get_version() returns DatasetInfo (was VersionInfo)
  • schema.get_output_schema() replaced by schema.analyze()
  • datasets.deploy() version param renamed to revision

Resolves #45 and #27

fordN added 2 commits April 8, 2026 13:34
- Fetch latest OpenAPI spec (185KB, 17 new endpoints)
- regenerate Pydantic v2 models
- fix breaking changes (stop PUT, delete_by_status, new schema contract)
- implement new RevisionsClient
- add job events/progress/create endpoints
- add dataset restore/list_jobs
- add CI spec-drift check workflow
@fordN fordN self-assigned this Apr 8, 2026
@fordN fordN added the adminAPI label Apr 8, 2026
fordN added 4 commits April 8, 2026 14:10
Run ruff format on models.py after generation in both CI and
Makefile so the committed (formatted) file matches what the
spec-check workflow produces.
Without a lock file, CI resolves latest dependency versions which
can differ from local, causing spec-check failures (e.g.
datamodel-code-generator producing different Optional syntax).
The generated timestamp changes on every run, causing the CI
spec-check to always detect a diff.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Keep admin-api in sync with amp upstream

1 participant