I’m running into a persistent Could not find schema with key $MY_SCHEMA_KEY in any repository; tried repositories Iglue Central [HTTP], $MY_RESPOSITORY [HTTP], Iglu Central - GCP Mirror [HTTP].
The thing is that the schema in question is indeed present in the repository (I’m running the Iglu Server as a Docker container, rather than the raw S3 bucket situation). So I guess the question that follows is, how do I provide my Stream Enrich service with a read-api key for my Iglu repository server?
Ah one further question: is it possible to have a single API key that grants read access to multiple vendor namespaces? If not, is the preferred alternative to re-list the registry with a separate API key and indicate the specific vendor prefix that the key applies to?
Hey @pearsonhenri it is indeed possible - you just need to generate a read key with the * vendor space - this should then be able to access any schema in your Iglu Server. Sort of like a super read key.
You can always assert if your key will work as expected by attempting to access schemas directly from the Iglu Server using the generated key before applying it to your Stream Enrich server.