Bug: scaffolder fails to read component.yaml from github

[ryanj]

Describe the bug

While using a template, the scaffolder fails to read the newly uploaded component.yaml from github.com

1. The scaffolder will create a new repo and upload it to github.com
2. After uploading the repo to github.com, the scaffolder should register the newly uploaded component.yaml file with RHDH.
3. The scaffolder will fail, reporting that the component.yaml file is unavailable on github.com.
4. Clicking on the link to the component.yaml file will reveal that the file was successfully created. Seems to indicate a race condition?

This issue was not reproducible when using GitLab

Expected Behavior

Uploaded assets should be immediately available via API - but there seems to be some delay on github.com.

Suggestion: The scaffolder should add a small delay before attempting to read the component.yaml from github.com, or add a retry in case of 404?

What are the steps to reproduce this bug?

1. Set up rhdh-0.1 on Azure (ARO)
2. Use a template to create a new component

Versions of software used and environment

quay.io/rhdh/developer-hub-rhel9:0.1 on Azure (ARO) via demo-setup

[ryanj]

This change offers a temporary resolution by adding a delay in the templating process: redhat-scholars/backstage-workshop@d9436a2

[ryanj]

Moving this bug report upstream: backstage/backstage#19678