-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
fix: Wrap errors when unmarshal Cloud Run deploy manifests fail. #9578
fix: Wrap errors when unmarshal Cloud Run deploy manifests fail. #9578
Conversation
🤖 I detect that the PR title and the commit message differ and there's only one commit. To use the PR title for the commit history, you can use Github's automerge feature with squashing, or use -- conventional-commit-lint bot |
Wrap errors returned from k8syaml.Unmarshal
…d-run-deploy-error' into jesseward/wrap-cloud-run-deploy-error Merging upstream
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR!
Could you do the same if it happens with a Cloud Run Job?
return nil, sErrors.NewError(fmt.Errorf("unable to unmarshal Cloud Run Job config"), &proto.ActionableErr{ |
return sErrors.NewError(fmt.Errorf("unable to unmarshal Cloud Run Job config"), &proto.ActionableErr{ |
thanks @mattsanta , newest commit captures the Cloud Run Job yaml unmarshal errors as well. |
Fixes: #9577
Related:
Merge before/after:
Description
Minor change to wrap errors for Cloud Run Service manifest parsing.
User facing changes (remove if N/A)
This will update log output for users of Cloud Deploy and vanilla Skaffold from the CLI.
Before
After
Will also expect that stackdriver logs will render the
error unmarshaling JSON: ...
string as well.