Reed Allman

> This is likely to turn into another holy war, but personally I dislike the idea of monotonic versioning of functions by the CLI. I'd rather see it taken away...

if 2 users want to test 'dev' versions of the function the answer at the moment is likely 'copy it to DevFunctionXxx' and have a 'ProdFunctionXxx' and set up some...

`fn test` am not sure of its fate, but I'm not sure if the scope is right here. In theory it seems useful to be able to test a container...

yeah, it would be nice if `func.yaml` was just configuration for a function/trigger rather than some weird unclear mix of local build fields and remote configuration fields. generating the Dockerfile...

tickets for each will be easier to track / knockout. we're 1/3 now

is the pull step before this? lazy and didn't see it in the diff (sorry). users shouldn't need to manually pull the init image and docker inspect will burp if...

closes https://github.com/fnproject/fn/issues/699 -- the image was never pushed to the registry. i can confirm that using this version of the cli, an image provided with a registry ends up in...

meh, this FN_REGISTRY idea is dumb. a hostname (without a port) and a user name will both look the same, i'm not sure it's possible to move forward... FN_REGISTRY is...

> I think making FN_REGISTRY fully qualified makes sense, eg: FN_REGISTRY=docker.io/NAMESPACE . > > Would that be enough to resolve all of this? Docker refers to it as namespace since...

I don't really like the whole FN_REGISTRY experience to begin with, asking the wrong dude. ya got the wrong lebowski