Jason Hall 4342ceff74 Implement "strict mode" ...

When ko is invoked in this mode, import paths must have the `ko://`
prefix. If a human marks an import path with `ko://` and ko can't
resolve the resulting import path, it fails. In "loose mode", such an
import path would be silently ignored and passed on to the resolved
YAML, often resulting in invalid image names (e.g., `image:
github.com/foo/bar`)

In loose mode, `ko://` prefixes are always ignored for
backward-compatibility.

2019-08-15 09:45:59 -04:00

..

options

Implement "strict mode"

2019-08-15 09:45:59 -04:00

apply.go

Implement "strict mode"

2019-08-15 09:45:59 -04:00

commands.go

Added command completion (#49)

2019-07-08 17:04:58 -07:00

completion.go

Added command completion (#49)

2019-07-08 17:04:58 -07:00

config.go

Bump ggcr depenency (#41)

2019-06-21 13:15:10 -07:00

create.go

Implement "strict mode"

2019-08-15 09:45:59 -04:00

delete.go

Move ko commands to pkg/commands (#29)

2019-04-26 15:56:15 -07:00

publish.go

Implement "strict mode"

2019-08-15 09:45:59 -04:00

publisher.go

Add go module support (#60)

2019-07-12 22:54:25 -07:00

resolve.go

Implement "strict mode"

2019-08-15 09:45:59 -04:00

resolver.go

Implement "strict mode"

2019-08-15 09:45:59 -04:00

run.go

Implement "strict mode"

2019-08-15 09:45:59 -04:00

version.go

Resolving #21 issue. Adding git-dir flag to always execute inside ko's directory in GOPATH

2019-05-17 05:54:03 +00:00