I would definitely add it to my roadmap

Thanks for your idea. I first thought that simply viewing data might not be useful as many IDEs already handle basic data previews. One of core goals was to access stored metadata directly from the file without necessarily scanning the data. Your idea of potentially mixing current implementation (using pyarrow) with DuckDB is very interesting:)

note: with duckdb you get network storage for free (ie delta table on s3 works the same as local) and i guess a smaller deps than pyarrow (might be wrong)

Check README.md please. brew install now supported!

Thanks for the feedback. I’ll support brew tap / install today or tomorrow:)

Thanks for sharing:) Your approach seems reasonable and extremely powerful for variable features. As you mentioned, using local Envoy proxy with Istio is an excellent choice. But my approach was for reducing all the extra setups and just ‘port-forward’ services with single binary. I was intended to help developers who might be less experienced with cloud-native complexities, or anyone who just wants a simple way to do testing against their clusters!