Skip to content

Conversation

@vknabel
Copy link
Contributor

@vknabel vknabel commented May 5, 2025

Description

Early exiting the loop resulted in only trying to sync one single node when using Metal-Edit permissions. Here the tag update was forbidden.

@vknabel vknabel marked this pull request as ready for review May 5, 2025 10:42
@vknabel vknabel requested a review from a team as a code owner May 5, 2025 10:42
@vknabel vknabel requested a review from majst01 May 5, 2025 10:43
@vknabel vknabel requested a review from majst01 May 5, 2025 11:56
@majst01 majst01 merged commit 3af3453 into master May 6, 2025
1 check passed
@majst01 majst01 deleted the do-not-abort-sync-on-tag-update-failure branch May 6, 2025 08:16
@Gerrit91
Copy link
Contributor

Gerrit91 commented May 6, 2025

To me this was kind of ok as these labels were never able to sync anyway and having this kind of thing does not really hurt. Can still be prevented in the API if we want it, but then there must be a data migration in the existing data of metal-api, which is also complex.

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