Flight Deck: moving to its own team space to support multiple Debian teams

[Arthur Diniz]

Hi all,




Flight Deck currently lives under the go-team namespace.

https://salsa.debian.org/go-team/flight-deck






What this means for go-team:


- The web interface at flight-deck.debian.net continues to work as before.

Migration details:







Existing repositories on Salsa won't be touched.





I'll be working on this incrementally over the next couple of weeks.



Thanks,
Arthur Diniz

I'm writing to let you know about a planned change to Flight Deck, the tool we've been using to manage our GitLab repositories on Salsa. I'm planning to move it to its own dedicated team/space so it can serve multiple Debian teams (not just ours). The goal is to make it a shared tool that any packaging team on Salsa can use to manage their repositories with the same automation we already benefit from (branch protection, badges, webhooks) consistent configuration, etc. - No impact on existing repositories managed by Flight Deck. All configurations and settings remain untouched. - There will be some internal changes, the folder structure and how Terraform/Tofu state names are derived will be updated. - I'll handle the state migration so existing states map correctly to the new structure, no manual action required from team members. - The go-team defaults (salsa-ci.yml, fast-forward merges, branch protection, badges, webhooks) are fully preserved. The Terraform state names are currently derived from the folder path (e.g. go-team-packages-d2). With the restructuring, these will need to be migrated to match the new paths. I'll do this transparently, either by renaming states in the backend or by re-importing them, so there's no drift or recreation of resources. Then other Debian teams will be able to onboard and manage their own repositories through Flight Deck. A lightweight approval mechanism will be added so team members can approve new repository creation requests for their team. Each team keeps full control over their own defaults and repository configurations. If you have questions or concerns, feel free to reply here or reach out directly.

OpenPGP_signature.asc
Description: OpenPGP digital signature