From b9692e574cb6751f60354375d7d00ac571f8aa03 Mon Sep 17 00:00:00 2001 From: Habib Ahmed Qureshi Date: Tue, 29 Dec 2020 18:45:30 +0100 Subject: [PATCH] reading named binding (#844) * reading named binding Reading named binding took me quite some time to actually get it to working, I believe adding this line would help other readers save some time * Update docs/reference/service_discovery.md Co-authored-by: John Luo --- docs/reference/service_discovery.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/reference/service_discovery.md b/docs/reference/service_discovery.md index f1abd06b..1921f314 100644 --- a/docs/reference/service_discovery.md +++ b/docs/reference/service_discovery.md @@ -232,7 +232,7 @@ We'll follow the example of the connection string for `postgres` is generated an 4. On startup, the environment variable configuration source reads all environment variables and translates them to the config key format (see table above). -5. When the application calls `GetConnectionString("postgres")`, the method will read the `connectionstrings:postgres` key and return the value. +5. When the application calls `GetConnectionString("postgres")`, the method will read the `connectionstrings:postgres` key and return the value. For the case of the named binding, if the application calls `GetConnectionString("postgres:mybinding")`, the method will read the `connectionstrings:postgres:mybinding` key and return the value. ## How it works: Deployed applications