Dave Protasowski

Logs ``` {"component":"peribolos","file":"k8s.io/test-infra/prow/cmd/peribolos/main.go:1297","func":"main.configureTeamMembers.func1","level":"info","msg":"Set dprotaso as a member of api-core-wg-leads(API Core WG Leads)","severity":"info","time":"2022-05-13T20:35:00Z"} [415](https://prow.knative.dev/view/gs/knative-prow/pr-logs/pull/knative_community/1067/pull-knative-peribolos/1525211406578749440#1:build-log.txt%3A415) {"client":"github","component":"peribolos","file":"k8s.io/test-infra/prow/github/client.go:910","func":"k8s.io/test-infra/prow/github.(*client).log","level":"info","msg":"EditTeam({0 Serving WG Leads serving-wg-leads closed \u003cnil\u003e 0xc000181880 })","severity":"info","time":"2022-05-13T20:35:00Z"} [416](https://prow.knative.dev/view/gs/knative-prow/pr-logs/pull/knative_community/1067/pull-knative-peribolos/1525211406578749440#1:build-log.txt%3A416) {"client":"github","component":"peribolos","file":"k8s.io/test-infra/prow/github/client.go:910","func":"k8s.io/test-infra/prow/github.(*client).log","level":"info","msg":"ListTeamMembersBySlug(knative, serving-wg-leads, member)","severity":"info","time":"2022-05-13T20:35:00Z"} [417](https://prow.knative.dev/view/gs/knative-prow/pr-logs/pull/knative_community/1067/pull-knative-peribolos/1525211406578749440#1:build-log.txt%3A417) {"component":"peribolos","file":"k8s.io/test-infra/prow/cmd/peribolos/main.go:209","func":"main.main","level":"fatal","msg":"Configuration failed: failed...

cc @cjwagner @fejta

I'd probably make things worse ;)

My mental model for using this tool is 1. Run dry-run to ensure config etc is valid 2. Apply the changes when 1 succeeds We do 1 in PR presubmits...

Likewise using the confirm flag prior to the dry run seems like a workaround

I guess multiple PRs is a decent enough workaround. I'll leave this issue open in case someone else is looking to pick up the work.

Splitting things up into a separate PRs didn't work. It seems like `--confirm=false` is broken? I created a new issue: https://github.com/kubernetes/test-infra/issues/26542

/lifecycle frozen

It also looks like the approval needs to occur any time there's a new change (ie. pushed a commit) on the PR.

> Our experience is that actions and Prow sometimes do have surprising and confusing behavior. What have you seen?