Issues with Concourse Org Automation

[stephanme]

Concourse Org Automation was enabled with #1545

This issue to track problems and decisions until the org automation workflow is green again and the concourse org is in the state as described by the WG charter + extra configuration in https://github.com/cloudfoundry/community/tree/main/orgs

[stephanme]

https://github.com/cloudfoundry/community/actions/runs/29721456601/job/88285158521 failed with:

{"client":"github","component":"peribolos","level":"info","msg":"GetOrg(concourse)","severity":"info","time":"2026-07-20T15:06:30Z"}
{"client":"github","component":"peribolos","level":"info","msg":"AppInstallationToken()","severity":"info","time":"2026-07-20T15:06:42Z"}
{"client":"github","component":"peribolos","level":"info","msg":"EditOrg(concourse, {concourse 7809479 MDEyOk9yZ2FuaXphdGlvbjc4MDk0Nzk= team@concourse-ci.org  contact@concourse-ci.org Worldwide Concourse An open-source continuous thing-doer, mostly used for CI/CD true true none false})","severity":"info","time":"2026-07-20T15:06:54Z"}
{"client":"github","component":"peribolos","level":"info","msg":"ListOrgInvitations(concourse)","severity":"info","time":"2026-07-20T15:07:06Z"}
{"client":"github","component":"peribolos","level":"info","msg":"ListOrgMembers(concourse, admin)","severity":"info","time":"2026-07-20T15:07:18Z"}
{"client":"github","component":"peribolos","level":"info","msg":"ListOrgMembers(concourse, member)","severity":"info","time":"2026-07-20T15:07:30Z"}
{"component":"peribolos","level":"fatal","msg":"Configuration failed: failed to configure concourse members: cannot delete 93 memberships or 0.903 of concourse (exceeds limit of 0.250)","severity":"fatal","time":"2026-07-20T15:07:42Z"}

The org automat would result in 8 members + 2 bots + a few admins (TOC). See org.out.yml attached to #1545. 93 current members of the concourse org would lose their membership.
@taylorsilva : Please confirm.

I would then adapt the peribolos configuration temporarily to allow 95% membership deletion and run again.

[taylorsilva]

That looks to be correct. The team had manually added A LOT of people over the years, mostly to our all team which is equivalent to the Contributor in the CF org. That's where most of the membership loss is coming from. All ex-Concourse team members (i.e. Vito) will also end up removed now.

[stephanme]

https://github.com/cloudfoundry/community/actions/runs/29763784061/job/88424711989 failed with:

{"client":"github","component":"peribolos","level":"info","msg":"ListTeams(concourse)","severity":"info","time":"2026-07-20T20:24:39Z"}
{"component":"peribolos","level":"fatal","msg":"Configuration failed: failed to configure concourse teams: cannot delete 7 teams or 1.000 of concourse teams (exceeds limit of 0.950)","severity":"fatal","time":"2026-07-20T20:24:51Z"}

I have to got for max-removal-delta=1

[taylorsilva]

@stephanme Everything looks good team and membership-wise in the Concourse org now.

I do have one question about how contributor membership works, since I think there will be folks that want contributor status in the Concourse org. Based on these files:

• https://github.com/cloudfoundry/community/blob/main/toc/ROLES.md

• community/orgs/contributors.yml

  Lines 203 to 204 in 34eb24c

  	concourse:
  	contributors:

Do users in the contributor list end up on a team in the Concourse org, or are they just added as members? Assuming the latter, just want confirmation. TY!

[stephanme]

User who want to become contributors should file a PR for contributors.yml or ask an approver to file the PR. WG leads or TOC merge the PR if conditions are met.

Details are documented in the RFCs:

• https://github.com/cloudfoundry/community/blob/main/toc/rfc/rfc-0002-github-members.md
• https://github.com/cloudfoundry/community/blob/main/toc/rfc/rfc-0008-role-change-process.md

[stephanme]

https://github.com/cloudfoundry/community/actions/runs/29824506527/job/88614624627 failed with:

{"component":"peribolos","level":"fatal","msg":"Configuration failed: failed to configure concourse team wg-concourse repos: [failed to configure concourse child team wg-concourse-leads repos: failed to update team 18628895(wg-concourse-leads) permissions on repo baggage-claim to admin: status code 404 not one of [204], body: {\"message\":\"Not Found\",\"documentation_url\":\"https://docs.github.com/rest/teams/teams#add-or-update-team-repository-permissions\",\"status\":\"404\"}, failed to configure concourse child team wg-concourse-bots repos: failed to update team 18628887(wg-concourse-bots) permissions on repo baggage-claim to write: status code 404 not one of [204], body: {\"message\":\"Not Found\",\"documentation_url\":\"https://docs.github.com/rest/teams/teams#add-or-update-team-repository-permissions\",\"status\":\"404\"}, failed to configure concourse child team wg-concourse-core-approvers repos: failed to update team 18628888(wg-concourse-core-approvers) permissions on repo baggage-claim to write: status code 404 not one of [204], body: {\"message\":\"Not Found\",\"documentation_url\":\"https://docs.github.com/rest/teams/teams#add-or-update-team-repository-permissions\",\"status\":\"404\"}]","severity":"fatal","time":"2026-07-21T16:32:26Z"}

There is no repo https://github.com/concourse/baggage-claim (only one archived https://github.com/concourse/baggageclaim).
https://github.com/cloudfoundry/community/blob/main/orgs/orgs.yml doesn't list a repo baggage-claim either.

I guess the issue is here: https://github.com/cloudfoundry/community/blob/main/toc/working-groups/concourse.md?plain=1#L100

Should have been detected by org-automation CI ...