Technical task using Git issue ops about git-issue-ops HOT 3 OPEN

Few concerns after looking at the task.

1. Are we talking about setting up GHE on-prem or using github.com
2. Keycloak is not a supported Idp for GitHub
3. SAML SSO requires either GHE cloud or on-prem
4. I can try setting up GHES on-prem by using a trial license if needed.
5. Is there any test lab available to implement this task.

from git-issue-ops.

Feedback from the customer

1. Are we talking about setting up GHE on-prem or using github.com

Use Github.com.

2. Keycloak is not a supported Idp for GitHub

Remove keycloak connection from the task.

3. SAML SSO requires either GHE cloud or on-prem

That’s right, use github.com instead.

4. I can try setting up GHES on-prem by using a trial license if needed.

Not required, but if time permits and resources are available.

5. Is there any test lab available to implement this task.

Use any of the cloud platforms.

from git-issue-ops.

With the new information update, Alternative A is not considered anymore for implementation. Alternative B will be used for setting up PoC with the following tasks

• Optional Kubernetes Cluster.
• Organization in github.com with user groups/teams.
• Artifactory in cloud (in K8 optional) that can communicate with github.com.
• Develop concept for issueops to
  • Read existing users from GitHub org members/roles/teams/outside collaborators.
  • Map the users to user groups.
  • on new issue, create artifactory repos, groups, permission targets according to users maps.
• Implement issueops based on above concept

from git-issue-ops.