-
Notifications
You must be signed in to change notification settings - Fork 286
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
pack inspect
does not provide ARGS
for npm project
#1976
Comments
Hi @kotapeter ! I managed to reproduce the error in the latest pack 0.32.0 version. |
Since [email protected] the The problem is that we get just In this case the
My proposal is to use the rest parts of |
@kotapeter thank you very much for this contribution!! ❤️ I am going to wait for @natalieparellano feedback here, because, I have some doubts about why she rolled back the commit that seems to fix this issue from the beginning. I do not remember the context of this. |
I vaguely recall that before Platform API 0.11, the build metadata label (io.buildpacks.build.metadata)
In Platform 0.10, how to display the process is just a mystery when Edit: if |
I ran into this issue myself this morning. It is indeed quite annoying. In case it helps others, the following command can grab the list from |
Summary
I can see the default web process command during the build time but the
pack inspect
does not show the same result. TheARGS
is empty.Reproduction
Steps
git clone https://github.com/kotapeter/pack-inspect-bug.git
cd pack-inspect-bug
pack build test --builder heroku/builder:22 --path=.
pack inspect test
Current behavior
ARGS
is emptyExpected behavior
ARGS
should displaystart
Environment
pack info
docker info
The text was updated successfully, but these errors were encountered: