Generate Fiori Deploy config Hangs with no error

[former_member755345]

Tutorials: https://developers.sap.com/tutorials/btp-app-launchpad-service.html
--------------------------
Hello,

I'm following the tutorials on developer.sap.com. I have all the application working locally and following step by step.

However, when I reach to the stage of creating the deploy configuration for both "Risks" and "Mitigation", it requires to run the command "fiori add deploy-config cf", the command simple stop responding and never returns back to the prompt.

I tried to increase change loglevel to verbose, but right after I provide the destination name, which is "cpapp-app-srv", then it stop working.

I'm at Step 10 of tutorial https://developers.sap.com/tutorials/btp-app-launchpad-service.html .

Any idea or file I should take a look? The "cpapp" deployment works fine, even DB... except I cannot integrate both UI5 and Fiori apps (Risks and Mitigation) to deploy the html5 content and srv.

~/DEV/demo-cap-3/cpapp/app/risks (master)
$ fiori add deploy-config
Adding deploy-config to the project.
info Add:Deploy-config Using: @sap/fiori:deploy-config
? Destination name cpapp-app-srv

$ npx fiori add deploy-config
npm info it worked if it ends with ok
npm verb cli [
npm verb cli   'C:\\Program Files\\nodejs\\node.exe',
npm verb cli   'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
npm verb cli   'prefix',
npm verb cli   '-g'
npm verb cli ]
npm info using npm@6.14.4
npm info using node@v14.1.0
npm verb exit [ 0, true ]
npm timing npm Completed in 76ms
npm info ok
npm verb cli [
npm verb cli   'C:\\Program Files\\nodejs\\node.exe',
npm verb cli   'C:\\Users\\<USER>\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js',
npm verb cli   'exec',
npm verb cli   '--',
npm verb cli   'fiori',
npm verb cli   'add',
npm verb cli   'deploy-config'
npm verb cli ]
npm info using npm@7.22.0
npm info using node@v14.1.0
npm timing npm:load:whichnode Completed in 0ms
npm timing config:load:defaults Completed in 1ms
npm timing config:load:file:C:\Users\<USER>\AppData\Roaming\npm\node_modules\npm\npmrc Completed in 3ms
npm timing config:load:builtin Completed in 3ms
npm timing config:load:cli Completed in 1ms
npm timing config:load:env Completed in 1ms
npm timing config:load:file:C:\Users\<USER>\DEV\demo-cap-3\cpapp\app\risks\.npmrc Completed in 0ms
npm timing config:load:project Completed in 1ms
npm timing config:load:file:C:\Users\<USER>\.npmrc Completed in 1ms
npm timing config:load:user Completed in 1ms
npm timing config:load:file:C:\Users\<USER>\AppData\Roaming\npm\etc\npmrc Completed in 2ms
npm timing config:load:global Completed in 2ms
npm timing config:load:validate Completed in 0ms
npm timing config:load:credentials Completed in 1ms
npm timing config:load:setEnvs Completed in 1ms
npm timing config:load Completed in 12ms
npm timing npm:load:configload Completed in 12ms
npm timing npm:load:setTitle Completed in 0ms
npm timing npm:load:setupLog Completed in 1ms
npm timing config:load:flatten Completed in 3ms
npm timing npm:load:cleanupLog Completed in 3ms
npm timing npm:load:configScope Completed in 0ms
npm timing npm:load:projectScope Completed in 1ms
npm timing npm:load Completed in 41ms
Adding deploy-config to the project.
info Add:Deploy-config Using: @sap/fiori:deploy-config
? Destination name cpapp-app-srv

[slavipande22]

Hi dszortykajd,

Thanks for your feedback and sorry for the delayed answer!

Please re-run the module Add the SAP Launchpad Service starting from the result of the MTA deployment branch. You can find a link to it in the beginning of the module Add the SAP Launchpad Service. Here's a screenshot for your reference:

If the issue still persists after that, please share your mta.yaml file so we can investigate further.

Best regards,

Svetoslav

[former_member755345]

I was able to workaround this issue with the following actions.

Gitrepo: https://github.com/SAP-samples/cloud-cap-risk-management/

Branch: launchpad-service

From there I copied the ui5-deploy.html and xs-app.json for both Risks and Mitigations Apps.

Then I was able to run npm run build:cf for both projects.

I also had to copy the mta.yaml file because mine was still missing the NS modules for each app.