Skip to content

Use pulumi state rename in repository rename notes #201

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
localden merged 1 commit into from
Sep 30, 2026
Merged

Use pulumi state rename in repository rename notes #201

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,8 +57,8 @@ The PR's `pulumi preview` comment shows the repository create. Once merged, the
- Repository names are lowercase kebab-case (`ext-*` for extensions, `experimental-ext-*` while experimental).
- At least one team or user must have `admin` permission (validated), so a managed repository is never ownerless.
- Removing the entry **archives** the repository rather than deleting it; deletion stays a manual org-owner action.
- Entries without `settings` are access-only: the repository pre-dates this config and Pulumi manages only its collaborators. Adding `settings` to such an entry does not adopt the repository — the deploy fails with a name-already-exists error. Adopt it with `pulumi import` first; that is out of scope for the PR flow above.
- The `repository` key of a managed entry is also the Pulumi resource name. Renaming it in place archives the old repository and creates a new one: rename on GitHub first, then move the state (`pulumi state mv`) before changing the key.
- Entries without `settings` are access-only: the repository pre-dates this config and Pulumi manages only its collaborators. Adding `settings` to such an entry does not adopt the repository. The deploy fails with a name-already-exists error. Adopt it with `pulumi import` first; that is out of scope for the PR flow above.
- The `repository` key of a managed entry is also the Pulumi resource name. Renaming it in place archives the old repository and creates a new one. To rename, do three things in order: rename the repository on GitHub, rename the resources in state with `pulumi state rename` (`repository-<old>` to `repository-<new>`, and `repo-<old>` to `repo-<new>`), then change the key.
- A repository archived by hand in GitHub stays archived (`archived` is ignored on refresh); un-archiving is a manual org-owner action.

## Cloudflare Access (security-room)
Expand Down
8 changes: 5 additions & 3 deletions src/config/repoAccess.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,9 +39,11 @@ export interface RepositoryAccess {
* that already exists does not adopt it: the deploy fails with a
* name-already-exists error. Adopt it with `pulumi import` first. The
* `repository` key of a managed entry is also the Pulumi resource name, so
* renaming it in place archives the old repository and creates a new one:
* rename on GitHub first, then move the state (`pulumi state mv`) before
* changing the key.
* renaming it in place archives the old repository and creates a new one.
* To rename, do three things in order: rename the repository on GitHub,
* rename the resources in state with `pulumi state rename`
* (`repository-<old>` to `repository-<new>`, and `repo-<old>` to
* `repo-<new>`), then change the key.
*/
settings?: RepositorySettings;
teams?: Array<{
Expand Down
Loading