Skip to content
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

Do not obscure error message #1227

Merged

Conversation

c0d1ngm0nk3y
Copy link
Contributor

Summary

When the lifecycle failed because there was no readable run image, the error was rather misleading:

-run-image is required when there is no stack metadata available

This was caused by hiding the underlying error.

Release notes

Improve error message in case run-image is not readable.


Related

Resolves #___


Context

When the run image is on a protected registry, the auth data must be provided to the lifecycle.

@c0d1ngm0nk3y c0d1ngm0nk3y requested a review from a team as a code owner October 27, 2023 08:31
Copy link
Member

@natalieparellano natalieparellano left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @c0d1ngm0nk3y 🙏🏼

@natalieparellano
Copy link
Member

Aye, now the linter is unhappy because the spacing for our exported message vars has changed and they were uncommented. You could update the commit sha here:

new-from-rev: 91593cf91797ca0a98ffa31842107a9d916da37b
if you don't feel like adding comments.

Signed-off-by: Ralf Pannemans <[email protected]>
@c0d1ngm0nk3y
Copy link
Contributor Author

Aye, now the linter is unhappy...

I have made some changes. IMHO, not the most useful linter warning though :) Please have a look.

@natalieparellano natalieparellano merged commit 2bf3ae7 into buildpacks:main Oct 27, 2023
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants