From db920df0533b303635009405c481df2ca7a1e151 Mon Sep 17 00:00:00 2001 From: Johan Haals Date: Wed, 29 Sep 2021 10:27:50 +0200 Subject: [PATCH] Update docs/features/software-catalog/external-integrations.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Johan Haals Co-authored-by: Fredrik Adelöw --- docs/features/software-catalog/external-integrations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/features/software-catalog/external-integrations.md b/docs/features/software-catalog/external-integrations.md index 1015af2630..508b04d77a 100644 --- a/docs/features/software-catalog/external-integrations.md +++ b/docs/features/software-catalog/external-integrations.md @@ -178,7 +178,7 @@ The catalog periodically refreshes entities in the catalog, and in doing so it c out to external systems to fetch changes. This can be taxing for upstream services and large deployments may get rate limited if too many requests are sent. Luckily many external systems provide ETag support to check for changes -which usually don't count towards the quota and saves resources both internally +which usually doesn't count towards the quota and saves resources both internally and externally. The catalog has built in support for leveraging ETags when refreshing external locations