Dr Nic Williams

Thanks for mentioning slightly nicer `/tmp/lifecycle/shell`. I'll follow up on slack about the second paragraph. I'm not sure if you're writing good news or bad news.

@emalm Is the issue above only for windows? Can `cf ssh` have a diff code path for windows vs linux containers; and auto-run the `/tmp/lifecycle/shell` command only when `cf ssh`...

Where is `/tmp/lifecycle/shell` implemented? Could we have a slightly different one, say `/tmp/lifecycle/ssh-shell` that is invoked transparently during `cf ssh` that doesn't reload `profile.d/*.sh` scripts into the same env? actually...

I like the idea of a flag; albeit I'd prefer that the default was this full environment idea, and a flag for have a raw container. I paid for Alfred...

What do you mean "figure out how to inject source code" with build-templates? Isn't this what we can already do now with `--directory=$PWD --template buildpack`?

Bah, did it again on a new cluster. Forgot to pre-install buildpack template and I sat there waiting until I looked in `knative-build` logs and found `"msg":"Failed to validate build:...

Relates to #46

I've created an upstream Build issue so perhaps we can get status updates with error messages https://github.com/knative/build/issues/471

The same category of issue occurs if `--template buildpack` references a BuildTemplate that doesn't exist yet. It only appears in build-controller logs: ``` knative-build/build-controller-79d6cc9d57-7svtq[build-controller]: {"level":"error","logger":"controller.build-controller","caller":"build/build.go:141","msg":"Failed to validate build: buildtemplates.build.knative.dev \"buildpack\"...

WIP, I tried adding `simple.knative.starkandwayne.com` to the existing virtualservice but a) the route never worked; and b) within a few seconds knative re-wrote the virtualservice to remove my appended `/spec/hosts`...