🐛 Bug Report: scaffolder "catalog:register" step fails to fetch component.yaml from github.com

[ryanj]

📜 Description

The scaffolder catalog:register action fails to read the newly uploaded component.yaml from github following a successful publish:github action

👍 Expected behavior

Files that are uploaded using the publish:github action are normally available without any delay (available for use in the following catalog:register scaffolder action step)

👎 Actual Behavior with Screenshots

The scaffolder's catalog:register action fails to fetch the newly published component.yaml from github (404 error)

👟 Reproduction steps

1. Set up backstage on Azure using GitHub and the following template: https://github.com/janus-idp/software-templates/blob/main/templates/github/spring-boot-backend/template.yaml
2. Use the template to create a new software component
3. The error should appear in the scaffolder output

📃 Provide the context for the Bug.

This bug was encountered by 100% of the users in a recent workshop. We were able to reproduce the issue with 100% reliability on our backup cluster as well.

We were able to successfully work around the issue by adding a small delay before reading from Github

🖥️ Your Environment

I experienced this bug while using backstage in a "production" deployment on Azure in "eastus2"

👀 Have you spent some time to check if this bug has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

Are you willing to submit PR?

No, but I'm happy to collaborate on a PR with someone else

[Rugvip]

I think I'd be good if we add a wait at the end of all publish/create/push actions where we poll the API to make sure that the repo or content we just created is ready to be used. That way any followup action won't need to worry about the repo or new repo contents potentially not existing yet.

Leaving this open for contributions

[github-actions]

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.