Unclear error in Backstage container start with gitlab plugin

[rafamonzb]

While starting container, it throws an error stating:

ForwardedError: Module 'gitlabFillerProcessor' for plugin 'catalog' startup failed; caused by Error: Missing required config value at 'integrations.gitlab' in 'env'

Using the new backend system, I've tried writing and commenting baseUrl and apiBaseUrl in different configurations, including both kubernetes internal routing and local external routing and couldn't get that error to go away. Also tried using http instead of the default in case it was due to our internal routing but still got nowhere.
Backstage is able to deploy and run normally without plugins.
I've also found the compiled code and saw that all tags in integrations.gitlab were being found and registered so I don't know what's causing this issue.

Full error message:

/app/node_modules/@backstage/backend-app-api/dist/index.cjs.js:689
                throw new errors.ForwardedError(
                      ^

ForwardedError: Module 'gitlabFillerProcessor' for plugin 'catalog' startup failed; caused by Error: Missing required config value at 'integrations.gitlab' in 'env'
    at /app/node_modules/@backstage/backend-app-api/dist/index.cjs.js:689:23
    at async /app/node_modules/@backstage/backend-app-api/dist/index.cjs.js:688:15
    at async processNode (/app/node_modules/@backstage/backend-app-api/dist/index.cjs.js:174:22)
    ... 5 lines matching cause stack trace ...
    at async #doStart (/app/node_modules/@backstage/backend-app-api/dist/index.cjs.js:657:5) {
  cause: Error: Missing required config value at 'integrations.gitlab' in 'env'
      at ConfigReader.getConfigArray (/app/node_modules/@backstage/config/dist/index.cjs.js:251:13)
      at ObservableConfigProxy.getConfigArray (/app/node_modules/@backstage/config-loader/dist/index.cjs.js:1251:30)
      at new GitlabFillerProcessor (/app/node_modules/@immobiliarelabs/backstage-plugin-gitlab-backend/dist/index.cjs.js:123:14)
      at Object.init [as func] (/app/node_modules/@immobiliarelabs/backstage-plugin-gitlab-backend/dist/index.cjs.js:185:37)
      at /app/node_modules/@backstage/backend-app-api/dist/index.cjs.js:688:37
      at async processNode (/app/node_modules/@backstage/backend-app-api/dist/index.cjs.js:174:22)
      at async Promise.all (index 3)
      at async processMoreNodes (/app/node_modules/@backstage/backend-app-api/dist/index.cjs.js:169:7)
      at async DependencyGraph.parallelTopologicalTraversal (/app/node_modules/@backstage/backend-app-api/dist/index.cjs.js:180:5)
      at async /app/node_modules/@backstage/backend-app-api/dist/index.cjs.js:681:11
      at async Promise.all (index 5)
      at async #doStart (/app/node_modules/@backstage/backend-app-api/dist/index.cjs.js:657:5)
}

I don't know how to move forward with this deployment so any idea is appreciated.

[antoniomuso]

Hi @rafamonzb, are you sure backstage is reading the right app-config.yaml? Can you put more details about your configurations?

[rafamonzb]

Hi @antoniomuso, thanks for the insight, I looked it up and it seems is a deployment issue. I was pretty sure I was passing the app-config correctly to the docker image but when deployed in Kubernetes it uses a different command to launch using "--config app-config-from-configmap.yaml", and it seems it isn't taking the app-config nor the production app-config. I'll update when I test that. Thanks again for answering :)