mirror of https://github.com/dotnet/tye.git
Browse Source
This tries to add some auto-detect magic to make common scenarios work without any extra configuration, which avoiding doing obtuse stuff. - We ignore the ports in launch settings (avoid conflict in the hello world multi-project case) - When we infer bindings based on launch settings we set them to auto-select a port - The user setting a port via tye.yaml will always win - Bindings that are not inferred from launch settings still work the same way (we don't auto-auto-select a port) - When we deploy we ignore https The HTTPS behavior might need discussion, but we haven't started looking at a recipe for HTTPs inside the cluster in k8s, and it's not clear whether we even want to. One could also make the argument that we should skip TLS locally because we're not doing it inside the cluster. Someone writing an app today that assumes TLS in their code (using https URLs, or gRPC + TLS) will have a non-trivial path to k8s for now anyway. So, skipping https bindings for k8s really just makes us more honest.pull/101/head
13 changed files with 121 additions and 82 deletions
Loading…
Reference in new issue