GoogleContainerTools / GoogleContainerTools/skaffold

Introduce new actionable error messages for common use cases, esp related to V1 -> V2 transition

Open
#7,655 0 comments 0 reactions 0 assignees View on GitHub
area/errors kind/todo needs-actionable-error priority/p3
Dominant language
Go
Stars
15.9k
Forks
1.7k
Avg merge
3d 9h
Merged PRs (30d)
10

Description

Current issues that come up pretty frequenty:
- when using render or deploy independantly, often errors stating `could not find image:`. In these cases user likely wants to use `build` and pass the artifacts file to `render` or `deploy` but we don't try to state this (perhaps unnecessary)
- for V2 if there is a field present eg: deploy.kubectl.manifests in addition to erroring likely makes sense to explain that for V2 you will need to use `skaffold fix`vs bumping to apiVersion directly

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.