We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
During the deployment task, there is an initial GET request made to determine if the BSP app is already deployed;
https://github.com/SAP/open-ux-tools/blob/main/packages/axios-extension/src/abap/ui5-abap-repository-service.ts#L179
In some cases, excluding HTTP 403/401 failures, the failed response can include ABAP response messages which are not displayed to the user.
In order to see these response messages, the developer needs to enable HTTP debugging as follows;
DEBUG=* npm run deploy
This will clearly show additional information that can be used to help to determine the root cause of why deployment has failed.
Provides better root cause analysis and prevents support issues.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Description (include screenshots)
During the deployment task, there is an initial GET request made to determine if the BSP app is already deployed;
https://github.com/SAP/open-ux-tools/blob/main/packages/axios-extension/src/abap/ui5-abap-repository-service.ts#L179
In some cases, excluding HTTP 403/401 failures, the failed response can include ABAP response messages which are not displayed to the user.
In order to see these response messages, the developer needs to enable HTTP debugging as follows;
This will clearly show additional information that can be used to help to determine the root cause of why deployment has failed.
Value
Provides better root cause analysis and prevents support issues.
Architecture Elaboration
Notes
Tasks
The text was updated successfully, but these errors were encountered: