An organisation data package must be built as part of the Data Collection Pipeline. A DAG for this job must be published via the airflow-dags repository.
Allow deployment reviewers to be specified for each GitHub repository.
Currently, a single list serves all GitHub repositories which doesn't allow for differentiation between different repositories and teams.
Note that GitHub only supports up to 6 users or teams to be deployment reviewers so it might be beneficial to utilise teams to increase the number of possible individual reviewers.
Tech Approach
Define separate reviewers lists in Terraform for each application/task repo
Use GItHub Teams to group together different types of reviewers, i.e. infrastructure-team, providers-team
Acceptance Criteria/Tests
Providers team are able to self-manage their own deployments to production in the submit repo
A few members of the infrastructure team continue to have reviewer privileges across all application/task repositories.
Creation of teams and assignment to reviewer lists is managed in Terraform code
Management of team membership is not managed in Terraform code
Resourcing & Dependencies
Are there any tickets that need to be completed before this one can be?
None
Are there any limitations as to who in the team can complete this ticket?
Yes, admin access to GitHub and AWS. Needs DevOps input.
Are there any dependencies on other teams to assist, approve or be handed over to once deployed?
Overview
An organisation data package must be built as part of the Data Collection Pipeline. A DAG for this job must be published via the airflow-dags repository.
Allow deployment reviewers to be specified for each GitHub repository.
Currently, a single list serves all GitHub repositories which doesn't allow for differentiation between different repositories and teams.
Note that GitHub only supports up to 6 users or teams to be deployment reviewers so it might be beneficial to utilise teams to increase the number of possible individual reviewers.
Tech Approach
Acceptance Criteria/Tests
Resourcing & Dependencies
Are there any tickets that need to be completed before this one can be?
None
Are there any limitations as to who in the team can complete this ticket?
Yes, admin access to GitHub and AWS. Needs DevOps input.
Are there any dependencies on other teams to assist, approve or be handed over to once deployed?
None known.