You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I run a bundle and specify --debug, that should cause the bundle to print out additional information, such as the commands being run.
mkdir mybuns && cd mybunsporter createporter install test --debug
# bundle output
The bundle output should include a line like /cnab/app ./helpers.sh install but it doesn't.
There seem to be a couple interrelated problems:
The RuntimeConfig.DebugMode value should be initialized to PORTER_DEBUG which is set in the bundle when run with --debug.
The verbosity configuration value isn't being overridden when set via --verbosity. Porter is only respecting the config file value and environment variable. This affects what porter prints out when running a bundle.
Some runtime structs and their functions have been updated to use telemetry, e.g. span.Info, but I suspect that when the TraceLogger is initialized inside a bundle, it isn't picking up the environment variables we are sending to set verbosity, otel, etc.
The text was updated successfully, but these errors were encountered:
When I run a bundle and specify --debug, that should cause the bundle to print out additional information, such as the commands being run.
The bundle output should include a line like
/cnab/app ./helpers.sh install
but it doesn't.There seem to be a couple interrelated problems:
The text was updated successfully, but these errors were encountered: