"No process was able to handle..." for github and gitlab
See original GitHub issueI had backstage sort of working in kubernetes but was experiencing some issues with templates. I noticed the image referred to in the helm charts is from April, so I’ve been trying to use a newer build.
- I’ve built a docker container from
tag/release-2021-12-16
using the instructions here. The container is available atcitihub/backstage:20211216
- I have it running in a Kubernetes cluster, deployed via the example helm chart.
- $GITLAB_TOKEN and $GITHUB_TOKEN are set inside the backend container, as verified by exec’ing into the container.
The log file has warnings that No processor was able to handle reading of github:...
when trying to load the sample data sets. This worked in the older build. When I try to add something from gitlab I get a similar error.
Expected Behavior
- Backstage processes .yaml files from github and gitlab.
Current Behavior
Backstage backend logs the following errors -
2021-12-21T21:59:08.690Z catalog warn No processor was able to handle reading of github:https://github.com/backstage/backstage/blob/master/plugins/github-actions/examples/sample.yaml type=plugin entity=location:default/generated-060bf5de1d298e45b4e44be6a1151632996f880f
2021-12-21T22:00:38.676Z catalog warn No processor was able to handle reading of gitlab/api:https://gitlab.com/my-group/backstage/-/blob/main/templates/hello-world/template.yaml type=plugin entity=location:default/generated-701b685ec94bceeb77d1de134b2874347835f4e0
Possible Solution
Steps to Reproduce
- Modify the example helm charts to use
citihub/backstage:20211216
as the backend image - Add auth.gitlab_token and auth.github_token to values.yaml
- Deploy the helm chart
- Navigate to “Register an existing component” and add a URL from either github or gitlab - error received
- Look at the log files
kubectl logs backstage-backend-abcd1234c-12345
Context
Backstage is unusable in this state because there is nothing configured to process files
Your Environment
- Built using Node v16
- Running in Azure Kubernetes Service v1.20.9
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (3 by maintainers)
i saw this little helper script that was lying around - maybe it can be helpful https://github.com/backstage/backstage/blob/master/scripts/migrate-location-types.js
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.