* Add Dapr integration to Tye
Adds a new `extensions` integration point. Currently all extensbility has
to be inside the Tye codebase. There's no functionality for loading or distributing
plugins.
Enable dapr for an application like:
```yaml
name: test_app
extensions:
- name: dapr
```
The dapr extension currently accepts and requires no additional options, and applies
to all services defined in the application.
What it does:
- In local run: starts a dapr sidecar for each project that does http
- In local run: sidecars start in the directory of tye.yaml, so dapr will look for
component manifests in ./components (relative to tye.yaml
- In deployment: adds required annotations to deployments
Some new features that were added to tye to enable this:
- Config: Ability to parse and conditionally run extensions
- Run: Ability to token replace env-vars into command line args
- Deploy: Ability to configure labels and annotations
* format
* Massage labesl:
* PR feedback
* Fix tests
- Separate 'Hosting.Model' from the YAML processing
- Introduce 'Config*' classes as YAML DTOs
- Refactor 'Hosting.Model' classes to be nullable-friendly
- Fix nullable warnings in M8s.Hosting
- Add support for registry from config
- Add application name to config
- Fix a bug with the wrong file-location used for tye.yaml
- Fix a bug with `tye deploy` at solution scope
Dasith Wijesiriwardena
Ryan Nowak
Justin Kotalik