-
Notifications
You must be signed in to change notification settings - Fork 283
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
Add --dry-run
option to pack commands
#681
Comments
Should this be supported for all commands, or only for some? For instance, |
Could you elaborate on "outputs any pack generated logs that would occur during a real execution"? Thinking about something like |
This is a really good idea! |
I think the stateless commands should still run, the solution would still be valid as there are no interactions with external dependencies in those cases. |
A |
@josegonzalez Agreed. This is an underlying premise with pack-interact-mode. |
@simonjjones @jromero @dfreilich Can we have a little more detail about what the original intent of @haliliceylan and I were following the thread and are lost. In the
|
Blocked (or perhaps more accurately, superseded) by buildpacks/rfcs#308 |
Description
I would like to validate the configuration and intended outcome of a command I plan to run without incurring the cost of executing against real code and resources
Proposed solution
Each
pack
command can be invoked with a--dry-run
argument which:Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: