This isn't optimal, but right now it's easy to get into problems using
tye because we don't generate manifests with digests.
As an example, if you don't have any versioning in your project, right
now we will *just* tag everything with 1.0.0. This can lead to pods
getting deployed with stale images, even though you pushed!
A better solution is for us to use digests instead of tags.
- 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