[Test automation] Configure and verify GitHub integration with Org data fetching

[Omar-AlJaljuli]

Description

Configured the environment to integrate the Janus-qe organization into the catalog. Created an automated test file that checks if the integration works. https://issues.redhat.com/browse/RHIDP-753.

Configuration followed from: https://access.redhat.com/documentation/en-us/red_hat_developer_hub/1.1/html-single/getting_started_with_red_hat_developer_hub/index#proc-add-source-control-rhdh-catalog_rhdh-getting-started

Which issue(s) does this PR fix

RHIDP-753

PR acceptance criteria

Please make sure that the following steps are complete:

• GitHub Actions are completed and successful
• Unit Tests are updated and passing
• E2E Tests are updated and passing
• Documentation is updated if necessary (requirement for new features)
• Add a screenshot if the change is UX/UI related

How to test changes / Special notes to the reviewer

[github-actions]

The image is available at: quay.io/janus-idp/backstage-showcase:pr-1336!

[github-actions]

The image is available at: quay.io/janus-idp/backstage-showcase:pr-1336!

[josephca]

@subhashkhileri can you provide a review? Thanks!

[Omar-AlJaljuli]

/retest

[Omar-AlJaljuli]

/retest

[Omar-AlJaljuli]

/retest

[github-actions]

The image is available at: quay.io/janus-idp/backstage-showcase:pr-1336!

[subhashkhileri]

/lgtm

[subhashkhileri]

/lgtm cancel

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from subhashkhileri. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• .ibm/OWNERS
• e2e-tests/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[subhashkhileri]

@josephca @Omar-AlJaljuli This test is already covered in github happy path : https://github.com/janus-idp/backstage-showcase/blob/main/e2e-tests/playwright/e2e/github-happy-path.spec.ts#L46

you would like to enhance or update the existing test or remove from old and keep it like this?

[Omar-AlJaljuli]

@josephca @Omar-AlJaljuli This test is already covered in github happy path : https://github.com/janus-idp/backstage-showcase/blob/main/e2e-tests/playwright/e2e/github-happy-path.spec.ts#L46

you would like to enhance or update the existing test or remove from old and keep it like this?

@subhashkhileri I believe the test you're talking about (in github happy path) tests the fetching of components from repos that have something like a catalog-info.yaml file Documentation for whats being tested in GH happy path. This PR tests if the organization that was integrated with is visible with the right config Documentation for whats being tested by this PR

[josephca]

@josephca @Omar-AlJaljuli This test is already covered in github happy path : https://github.com/janus-idp/backstage-showcase/blob/main/e2e-tests/playwright/e2e/github-happy-path.spec.ts#L46
you would like to enhance or update the existing test or remove from old and keep it like this?

@subhashkhileri I believe the test you're talking about (in github happy path) tests the fetching of components from repos that have something like a catalog-info.yaml file Documentation for whats being tested in GH happy path. This PR tests if the organization that was integrated with is visible with the right config Documentation for whats being tested by this PR

@subhashkhileri @Omar-AlJaljuli I think Omar is right. For example, the 'github happy path' is getting the group from

backstage-showcase/catalog-entities/groups/janus-authors.yaml

Line 6 in ef76d0e

name: janus-authors

- not from the 'githubOrg'.