8000
Skip to content

lxd: Require all cluster member to process forced project delete notifications#17091

Merged
tomponline merged 1 commit intocanonical:mainfrom
kadinsayani:fix/incorrect-cluster-notifyalive-usage
Nov 27, 2025
Merged

lxd: Require all cluster member to process forced project delete notifications#17091
tomponline merged 1 commit intocanonical:mainfrom
kadinsayani:fix/incorrect-cluster-notifyalive-usage

Conversation

@kadinsayani
Copy link
Copy Markdown
Member

No description provided.

…fications

Signed-off-by: Kadin Sayani <kadin.sayani@canonical.com>
@kadinsayani kadinsayani marked this pull request as ready for review November 27, 2025 15:09
@tomponline tomponline merged commit 1589036 into canonical:main Nov 27, 2025
68 of 70 checks passed
@markylaing
Copy link
Copy Markdown
Contributor

This PR has just made me think. With @MusicDin changing the client methods to return an operation, is it worth changing project deletion to be an operation at the same time? Just because force deletion could take a while for a large project.

@tomponline
Copy link
Copy Markdown
Member
tomponline commented Nov 28, 2025

at the same time

That time has already passed im afraid.

I am not against it in principle but we must avoid the drip-drip-drip breaking of the API every release (we saw how disruptive it was even before pushing to stable as it required new releases of pylxd and terraform).

@tomponline
Copy link
Copy Markdown
Member

I think if we are going to do this we should bite the bullet and make all mutating API endpoints use operations in one go.

@kadinsayani kadinsayani deleted the fix/incorrect-cluster-notifyalive-usage branch November 28, 2025 14:23
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.

3 participants

0