From f7132e30e78ad4fea7d5b39bf59cf7b623ecbc72 Mon Sep 17 00:00:00 2001 From: Sebastian Stabinger Date: Thu, 9 Nov 2023 15:00:54 +0100 Subject: [PATCH] Expands options for providing Azure OCR endpoint and key, updates README.md and CHANGELOG.md accordingly --- CHANGELOG.md | 2 +- README.md | 6 ++++++ 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index fbb5a24..96573d2 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -4,7 +4,7 @@ The version numbers are according to [Semantic Versioning](http://semver.org/). ## Next Release ### Added - +- Extended the possibilities on how to provide endpoint and key for Azure OCR in addition to the `credentials.json`. Have a look at the README.md for details. ### Changed ### Fixed diff --git a/README.md b/README.md index 8442a3a..cc71914 100644 --- a/README.md +++ b/README.md @@ -35,3 +35,9 @@ The credentials for Google OCR will be obtained from one of the following: - The environment variable `GOOGLE_APPLICATION_CREDENTIALS` - A credentials file `~/.config/gcloud/credentials.json` - A credentials file `/credentials.json` + +### AzureOCR +Credentials etc. for Azure OCR will be obtained from one of the following (in this order): +- From the `endpoint` and `key` arguments when creating AzureOCR +- From the environment variables `AZURE_OCR_ENDPOINT` and `AZURE_OCR_KEY` +- From the credentials file `~/.config/azure/ocr_credentials.json` that contains the keys `endpoint` and `key`