Hi experts,
I'm deploying the mta project.
The app contents (ui elements) was deployed well before, but suddenly it doesn't work.
This is my mta.yaml file.
---
_schema-version: '3.1'
ID: SeatReservationApp
version: 1.0.0
description: "A simple CAP project."
parameters:
enable-parallel-deployments: true
build-parameters:
before-all:
- builder: custom
commands:
- npm install --production
- npx -p @sap/cds-dk cds build --production
modules:
- name: SeatReservationApp-srv
type: nodejs
path: gen/srv
parameters:
buildpack: nodejs_buildpack
build-parameters:
builder: npm-ci
provides:
- name: srv-api # required by consumers of CAP services (e.g. approuter)
properties:
srv-url: ${default-url}
requires:
- name: SeatReservationApp-db
- name: SeatReservationApp-auth
- name: SeatReservationApp-db-deployer
type: hdb
path: db #gen/db
parameters:
buildpack: nodejs_buildpack
requires:
- name: SeatReservationApp-db
properties:
TARGET_CONTAINER: SeatReservationApp-dev
build-parameters:
ignore: ["default-env.json", ".env"]
- name: SeatReservationApp
type: approuter.nodejs
path: app/ # from cds.env.folders. Consider also cds.env.build.target -> gen/app
parameters:
keep-existing-routes: true
disk-quota: 256M
memory: 256M
requires:
- name: srv-api
group: destinations
properties:
name: srv-api # must be used in xs-app.json as well
url: ~{srv-url}
forwardAuthToken: true
- name: SeatReservationApp-auth
resources:
- name: SeatReservationApp-db
type: com.sap.xs.hdi-container
parameters:
service: hana
service-plan: hdi-shared
properties:
hdi-service-name: ${service-name}
- name: SeatReservationApp-auth
type: org.cloudfoundry.managed-service
parameters:
service: xsuaa
service-plan: application
path: ./xs-security.json
config:
xsappname: SeatReservationApp-${org}-${space}
tenant-mode: dedicated
The module managedAppCAPProject-app-content is the module that is related to app contents.
When I build the MTA project with this mta.yaml file, the seats.zip artifact is created but it is 0 bytes.
With this resource, The deployed app has no ui elements although other elements are deployed well.
I wonder why the resource file is 0 bytes unlike before.
If you know about this issue, please share the solution.
Thanks,
Sunyoung.