-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error message is hard to decipher #2055
Comments
@wfernandes I agree there is room for improvement there. In the meantime let me point out to #1994 where I'm starting to document how the new clusterctl works. IT is explained e.g. which provider you can use (you are not allowed to pass YAML anymore) Also, #2027 introduced a hack to make it possible to test the new clusterctl even if there are not yet v1 alpha3 releases of the providers |
@wfernandes #2048 is going to fix the error message |
/close cluster-api/cmd/clusterctl/pkg/client/common.go Lines 70 to 72 in 1bab288
|
@wfernandes: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
What steps did you take and what happened:
kind create cluster
make release-manifests
clusterctl init -b out/bootstrap-components.yaml --core out/core-components.yaml --infrastructure=aws
Got the following error:
It is very hard to decipher which
name
field is breaking this rule. The user has to go through all the yaml and probably even look up aws release manifest.What did you expect to happen:
For such an error, it would be nice to display the name of the field/component that the error is occurring on.
Environment:
kubectl version
):/etc/os-release
):/kind bug
/area clusterctl
The text was updated successfully, but these errors were encountered: