Skip to content

Add bypassGHErrors to scale set deletion - #929

Merged
gabriel-samfira merged 1 commit into
cloudbase:mainfrom
LucaCappelletti94:upstream/garm-scaleset-delete-bypass
Oct 24, 2026
Merged

gabriel-samfira merged 1 commit into
cloudbase:mainfrom
LucaCappelletti94:upstream/garm-scaleset-delete-bypass

Conversation

@LucaCappelletti94

Copy link
Copy Markdown
Contributor

Another paper cut encountered while moving configuration between orgs.

bypassGHErrors on DELETE /scalesets/{id} (--bypass-github-errors in garm-cli) removes a scale set even if GitHub fails to delete it, like bypassGHUnauthorized does for runners. Without it, a scale set whose repository was renamed or transferred blocks deleting that repository.

Its is stacked on #928, and de facto only consists of 66e1aff

@gabriel-samfira

Copy link
Copy Markdown
Member

Needs rebase. My bad. I used rebase and merge for your first PR.

@LucaCappelletti94

Copy link
Copy Markdown
Contributor Author

No worries, that was the intended sequence since I could not truly stack them.

@LucaCappelletti94
LucaCappelletti94 force-pushed the upstream/garm-scaleset-delete-bypass branch from 66e1aff to 06fafc7 Compare October 23, 2026 20:42
@LucaCappelletti94

Copy link
Copy Markdown
Contributor Author

ping @gabriel-samfira

@gabriel-samfira gabriel-samfira left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@gabriel-samfira
gabriel-samfira merged commit 33ec092 into cloudbase:main Oct 24, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants