fmorillo7694 commented on PR #236:
URL:
https://github.com/apache/flink-connector-aws/pull/236#issuecomment-5830902181
## Fresh end-to-end evidence vs real AWS Glue Schema Registry
All three SQL-format e2e suites re-run today against **real AWS Glue Schema
Registry** (eu-central-1, `default-registry`) on the current head, in one
combined invocation:
```
IT_CASE_GLUE_SCHEMA_USE_DEFAULT_CREDENTIALS=true
IT_CASE_GLUE_SCHEMA_REGION=eu-central-1 \
mvn clean verify -Prun-aws-end-to-end-tests \
-pl
flink-connector-aws-e2e-tests/flink-formats-avro-glue-schema-registry-e2e-tests,flink-connector-aws-e2e-tests/flink-formats-json-glue-schema-registry-e2e-tests,flink-connector-aws-e2e-tests/flink-formats-protobuf-glue-schema-registry-e2e-tests
\
-am -Dtestcontainers.version=1.20.4
```
| Suite | Result | Time |
|---|---|---|
| `GlueSchemaRegistryAvroSqlKinesisITCase` | **9/9** | 130.2 s |
| `GlueSchemaRegistryJsonSqlKinesisITCase` | **6/6** | 264.1 s |
| `GlueSchemaRegistryProtobufSqlKinesisITCase` | **5/5** | 100.9 s |
`BUILD SUCCESS` — total 12:23 min, finished 2026-09-25T11:50:58+02:00. Data
plane on Localstack Kinesis; every schema operation (create, register version,
get-by-definition, delete) against the real service. The registry was verified
free of test schema leftovers afterwards. Screenshot of the run to follow in
the next comment.
The run also exercised the three new commits just pushed:
- **`aws.credentials.*` now reach the schema fetcher** —
`GlueSchemaRegistrySchemaFetcher` (the `schema.fetchFromRegistry=true` path)
built its `GlueClient` on the implicit default chain, ignoring configured
credential options while the ser/deser facades honored them. It now resolves
credentials through the same `AWSGeneralUtil.getCredentialsProvider` path. No
behavior change for default configs.
- **Chinese docs completed** — `content.zh` carried only the formats
`_index.md`; the three per-format pages are now present (English content, per
the convention for not-yet-translated pages).
- **`IT_CASE_GLUE_SCHEMA_USE_DEFAULT_CREDENTIALS=true`** — the e2e suites
can now run off the AWS default credential provider chain (SSO, instance
profiles, `credential_process`) instead of requiring extracted access keys;
explicit `IT_CASE_GLUE_SCHEMA_*` keys remain the primary gate. Today's run used
this gate, so it is itself the verification. Mirrors the same option on the
Glue catalog e2e module in #206.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
