Default the porter-debug flag using --debug #244
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ghost
assigned 
carolynvs
changed the title
carolynvs
force-pushed
the
default-debug-param
branch
2 times, most recently
from
2e926a6 to
aceca60
Compare
carolynvs
changed the title
carolynvs
force-pushed
the
default-debug-param
branch
from
aceca60 to
7d82d96
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This finishes up the work of getting
porter install --debughooked up completely between the client side and the runtime (inside the bundle) via a CNAB parameter. Check out the output from our test-cli to see that now when we run our integration tests we get debug output from inside the bundle! 🎉