* 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 <johluo@microsoft.com>
CONNECTIONSTRING comes as CONNECTIONSTRINGS in the environment variable.
(Discovery during debugging tye run --debug (code is .NET 5.0.100) via System.Environment.GetEnvironmentVariable
CONNECTIONSTRING__POSTGRES -> CONNECTIONSTRINGS__POSTGRES
* Use environment variables for secrets
- Updating in place does not apply to connection strings specifically since they are usually configured at startup as singletons.
- This brings consistency with the development experience.
- Gets rid of AddTyeBindings
- "Less secure", sure but to be pedantic env variables are stored in virtual file on disk while the process is running. I'd argue if you want full security then use keyvault/vault/name your secret store.
Fixes#313
* Removed the last AddTyeSecrets call
Implements two flavor of library support for service-discovery:
- GetConnectionString (arbitrary strings) augmenting existing
functionality already in asp.net core
- GetServiceUri (uris) can be combined
from a protocol/host/port triple
See the **extensive** doc `service_discovery.md` that is filled out in this PR. That documents pretty much everything about how this works now.
This adds a basic tutorial for getting started with tye.
There are a few gaps we need to follow on, specifically:
- Organization of documents
- Content of tye deploy instructions
- Any follow up tutorials
Habib Ahmed Qureshi
Sahan Serasinghe
Alec Papierniak
Ryan Nowak
David Fowler
Justin Kotalik