Open synackSA opened 1 month ago
Could you double check that your GitHub integration is set up and both authenticated towards you GitHub instance and authorized to view the target repositories? Only seeing public repositories would indicate that that might now be the case.
📜 Description
We have a on-prem instance of Github (which will soon be migrated to Github Enterprise), with several repos being marked as either
private
orinternal
. With a previous version of Backstage, we were able to ingest these repos just fine. I have updated the backstage version and for some reason that I can not figure, those same repos are not being ingested. The Github token is the same, I'm fairly confident the token permissions are fine (I can query the repos via the API) and as soon as I switch the repo to public, it's ingested into Backstage.I've tried adding a
filter
forvisibility
, where I listedpublic
,private
, andinternal
, but that didn't seem to make any difference. I double checked that branches, but that was correct too.👍 Expected behavior
Repos marked as
private
orinternal
are ingested the same as a repo marked aspublic
👎 Actual Behavior with Screenshots
N/A
👟 Reproduction steps
AXP
org and mark it asprivate
orinternal
catalog-info.yaml
to repo📃 Provide the context for the Bug.
No response
🖥️ Your Environment
👀 Have you spent some time to check if this bug has been raised before?
🏢 Have you read the Code of Conduct?
Are you willing to submit PR?
None