@big-architect-71258 @elegant-window-55250 @cuddly-flower-91328 bumping this issue again hoping this could get priority: https://github.com/pulumiverse/infra/issues/298

@limited-rainbow-51650 I did a quick research at GitHub and their documentation about those "bot accounts" is ... let's simply call it confusing. What type of "bot account" is needed here? As far as I understood the "bot account" shall be used to run the scripts (worklow) from

ci-mgmt

to create PRs that will (auto-)update the build infrastructure and even the (bridged) provider itself. Main issue from my side is right now, aside I don't know what "bot user" we need here, how do we do this in a secure manner, i.e. we need a controlled way to "onboard" Pulumiverse provider repos onto the "bot account" and to

ci-mgmt

@big-architect-71258 maybe put this conversation on the issue.

Let me copy my answer there

@big-architect-71258 @elegant-window-55250 https://github.com/pulumiverse/infra/issues/298#issuecomment-3274556675

@limited-rainbow-51650 @elegant-window-55250 left a comment

@big-architect-71258 any follow up on closing the loop? IMO the only thing left to do is to create a fine grained access token for the "bot" github app and configure it in the

pulumiverse

org level secrets under the name

PULUMI_PROVIDER_AUTOMATION_TOKEN

. See my last comment on the issue: https://github.com/pulumiverse/infra/issues/298#issuecomment-3279070207

@limited-rainbow-51650 added a comment 🙂 @elegant-window-55250 @cuddly-flower-91328 I need your opinions on this matter plz 🙏🏼