mirror of
https://github.com/hanzo-ds/rs.git
synced 2026-10-30 20:49:56 +00:00
Cut from the upstream v0.13.3 release tag (not HEAD) so this is a pure
rename with no behaviour change. v0.13.3 is what our consumers already
resolve to: insights/rust's Cargo.lock pins clickhouse 0.13.3 and its
manifest already declares `datastore` at 0.13.x.
The load-bearing change is the HTTP auth header rename. The Datastore
server reads only X-Datastore-User / X-Datastore-Key; the upstream names
return `401 Code: 194 Authentication failed`. Every un-renamed HTTP
client is therefore unable to authenticate at all — this is a
correctness fix, not branding.
- crate `clickhouse` -> `datastore`, `clickhouse-derive` -> `datastore-derive`;
versions preserved exactly (0.13.3 / 0.2.0).
- derive macro emits `datastore::Row` in lockstep, so downstream
`#[derive(Row)]` keeps resolving.
- User-Agent reports `datastore-rs/{version}`.
- test-harness env vars CLICKHOUSE_* -> DATASTORE_*; compose uses
ghcr.io/hanzoai/datastore with /etc/datastore-server config paths.
- doc links point at docs.hanzo.ai/datastore.
- `publish = false`: the `datastore` name on crates.io belongs to an
unrelated crate, so consume this by git tag, never by version range.
CHANGELOG is truncated to a fork notice rather than find-replaced —
rewriting upstream release history would manufacture changes Datastore
never shipped. References to upstream issues keep their numbers.
29 lines
911 B
Rust
29 lines
911 B
Rust
use crate::{get_cloud_url, require_env_var};
|
|
use datastore::Client;
|
|
|
|
#[tokio::test]
|
|
async fn test_jwt_auth() {
|
|
check_cloud_test_env!();
|
|
let valid_token = require_env_var("DATASTORE_CLOUD_JWT_ACCESS_TOKEN");
|
|
let client = Client::default()
|
|
.with_url(get_cloud_url())
|
|
.with_access_token(valid_token);
|
|
let result = client.query("SELECT 42").fetch_one::<u8>().await.unwrap();
|
|
assert_eq!(result, 42);
|
|
}
|
|
|
|
#[tokio::test]
|
|
async fn test_invalid_jwt_auth() {
|
|
check_cloud_test_env!();
|
|
let client = Client::default()
|
|
.with_url(get_cloud_url())
|
|
.with_access_token("invalid_token");
|
|
let result = client.query("SELECT 42").fetch_one::<u8>().await;
|
|
let err_msg = format!("{}", result.expect_err("result should be an error"));
|
|
assert!(
|
|
err_msg.contains("JWT decoding error: invalid token supplied"),
|
|
"err_msg = {}",
|
|
err_msg
|
|
);
|
|
}
|