A TUI for Amp

[abarmat]

Amp : Command & Control

I started this as an experiment since I wanted to play with Amp and I love TUIs.

The first feature was a dataset viewer but then I got carried away and added more features, that's why you will see a quite big ui.rs. Review this PR considering that I will refactor the UI into components to encapsulate drawing to the terminal and event handling.

Summary

This PR introduces ampcc, a new Terminal User Interface (TUI) application for Amp, and extracts the admin client into a separate reusable crate.

• Terminal-based user interface for interacting with Amp nodes
• Splash screen with logo display
• Multiple panes with active pane concept and Tab/mouse navigation
• Dataset schema viewer pane
• Workers and jobs display when connected to a node
• Loading indicator for async operations
• Scrollable content views with scrollbars when content overflows
• Syntax highlighting for manifest files using syntect
• Custom theme using The Graph color palette
• Performance optimization with state-based UI redrawing
• Error display in footer area

Admin Client Extraction

• Extracted admin client code from ampctl into a new admin-client crate
• Modules included: auth, datasets, jobs, manifests, providers, workers
• Enables code reuse between ampctl and the new ampcc TUI

Added

• crates/bin/ampcc/ - New TUI application (app.rs, config.rs, main.rs, registry.rs, ui.rs)
• crates/admin-client/ - Extracted admin client library

[CLAassistant]

All committers have signed the CLA.

[LNSD]

Thanks for the PR, @abarmat. The split of the admin-client into a separate crate is something that I have been deferring. Finally, the time has come 🙌🏼

I would suggest creating a crates/clients/ directory where we place the different system clients (e.g., crates/clients/admin for the admin-client crate and crates/clients/flight for the flight-client crate).

[LNSD]

Note that one of the unit tests is failing because it requires all the workspace crate names to be listed here to pass:

amp/crates/core/monitoring/src/logging.rs

Lines 65 to 91 in 92f5c94

	const AMP_CRATES: &[&str] = &[
	"admin_api",
	"amp_client",
	"ampctl",
	"ampd",
	"ampsync",
	"ampup",
	"arrow_to_postgres",
	"auth_http",
	"common",
	"controller",
	"dataset_store",
	"datasets_common",
	"datasets_derived",
	"datasets_raw",
	"dump",
	"eth_beacon_datasets",
	"evm_rpc_datasets",
	"firehose_datasets",
	"js_runtime",
	"metadata_db",
	"monitoring",
	"server",
	"solana_datasets",
	"tests",
	"worker",
	];

[abarmat]

@LNSD I fixed the test and moved the admin and flight clients to the /crates/clients folder. Unsure about if this change breaks any external dependencies.

[abarmat]

@LNSD I'm checking the reason why the tests are failing

[LNSD]

The current test failures are unrelated to the changes. The CI is unable to access the secrets because your PR is from a fork.

[LNSD]

The failing tests are unrelated to the PR changes. Thanks for your contribution @abarmat.

LGTM ✅

[LNSD]

I can confirm that the tests are passing after merging into main ✅

• https://github.com/edgeandnode/amp/actions/runs/20296071121/job/58289979534
• https://github.com/edgeandnode/amp/actions/runs/20296071121/job/58289979533