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

Unified log output for all buildpacks used (ideally even between language families) #766

Closed
c0d1ngm0nk3y opened this issue May 26, 2023 · 4 comments

Comments

@c0d1ngm0nk3y
Copy link

When using the nodejs, you get a different log output compared to java. It varies even between buildpacks since the ca-certificates buildpack is used in both meta buildpacks.

Describe the Enhancement

All buildpacks should make use of the nicer log output of libpak/bard.

Possible Solution

How about moving libpak/bard to a separate repository to be used in all buildpacks and then bit by bit use this instead until we can remove libpak/bard and 'packit/scribe' altogether?

Motivation

If you try the npm sample, you will get somewhat confusing log output which is caused by the first buildpack to use a different logger.
In addition, if you use java and nodejs, the log output is not as unified than it could be. That would make a better user experience.

@loewenstein
Copy link

@c0d1ngm0nk3y I brought this up in the working group meeting and @sophiewigmore's suggestion was to propose this as an RFC (that would likely need a longer period of discussion on convergence).

@mhdawson
Copy link
Member

mhdawson commented Aug 6, 2024

@c0d1ngm0nk3y is this still something you plan on pursuing?

@sophiewigmore
Copy link
Member

Personally I had wanted to propose an RFC and then got really busy with other initiatives and never got to it. I'd love to see someone in the community push this forward if they're so inclined

@c0d1ngm0nk3y
Copy link
Author

@loewenstein-sap @sophiewigmore
I opened paketo-buildpacks/rfcs#308, so this can be probably closed.

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

No branches or pull requests

4 participants