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
The information provided by the deployer is useful when everything works as expected. But when the deployer is failing, it's unclear what is happening internally. It would be helpful for troubleshooting purposes to see information such as:
HTTP request/response information
Config values used and where they are sourced from
And any other useful actions being taken
Preferably this would also be triggered by the inclusion of the DEBUG=* environment variable that is frequently used for diagnostic purposes in the Heroku CLI (or the Java plugin for the CLI configures some verbose flag based on DEBUG).
The text was updated successfully, but these errors were encountered:
The information provided by the deployer is useful when everything works as expected. But when the deployer is failing, it's unclear what is happening internally. It would be helpful for troubleshooting purposes to see information such as:
Preferably this would also be triggered by the inclusion of the
DEBUG=*
environment variable that is frequently used for diagnostic purposes in the Heroku CLI (or the Java plugin for the CLI configures some verbose flag based onDEBUG
).The text was updated successfully, but these errors were encountered: