Update repoAccess for experimental-ext-tasks rename to ext-tasks#125
Merged
Conversation
Pulumi PreviewClick to expand preview output |
dsp-ant
added a commit
that referenced
this pull request
Jun 25, 2026
The repo was renamed to ext-tasks in #125, but Pulumi state still holds the old RepositoryCollaborators resource. The first 'pulumi up' (which runs before refresh) tries to delete it and 404s, blocking all deploys. Drop it from state explicitly before 'make up'. Idempotent via '|| true'; remove this line after one successful deploy.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The repository was renamed from
experimental-ext-taskstoext-tasks. GitHub redirects GET requests on the old name, but the team-repo DELETE endpoint the Pulumi github provider uses returns 404 against the old name. This has been failing the Deploy workflow since June 9, blocking propagation of every merge since then.After this lands, Deploy should succeed and the changes from #122 and #124 will propagate.
There is also a config-vs-reality drift on this repo:
lead-maintainershas admin access onext-tasksin GitHub but is not in this config. Once Deploy is pointed at the correct repo name, the--refreshstep will reconcile that. Iflead-maintainersshould keep access, a follow-up PR can add it to the config.