"Add team for timestamp codeowners" GHA job failure: 422 Validation Failed about community HOT 6 CLOSED

/assign

from community.

Analyzing this with the previous failure, you can see that "pulumi up on sigstore/github-prod" fails on both at the same stage, which is trying to upgrade the sigstore-oncall permission from "push" to "write" for the "helm-charts" repository:

 ~ github:index/teamRepository:TeamRepository: (update)
          [id=6693572:helm-charts]
          [urn=urn:pulumi:github-prod::sigstore-github-sync::github:index/teamRepository:TeamRepository::helm-charts-sigstore-oncall]
        ~ permission: "push" => "write"
          repository: "helm-charts"
          teamId    : "6693572"

from community.

-Doing some cursory research, my first thought experiment would be to manually remove the oncall group from membership to the helm-charts GitHub repository, and re-run the script to see if the script works or outputs differently in a way that could help us determine what it's stuck on.

@priyawadhwa - would it be possible to do this?

The only other theory I have is that Github may be complaining that the Team ID and/or Team name do not match it's expectation (hence 422 "Validation Failed"). Looking at https://github.com/orgs/sigstore/teams/sigstore-oncall however, the name and the teamId value of 6693572 matches.

from community.

Here's the API reference: https://docs.github.com/en/rest/teams/teams#add-or-update-team-repository-permissions - it does not mention the 422 status code, but that doesn't mean much.

from community.

I think Carlos might have fixed this with #145!

from community.

Yep looks like the most recent run was green (https://github.com/sigstore/community/actions/runs/3177181864) , I think we're good. Going ahead and closing this issue :)

from community.