Repository navigation
feat(audit-logs): label Operator update events - #3104
Merged
Merged
Conversation
Bump qovery-typescript-axios to 1.1.1010 for the OPERATOR_UPDATE and MAINTENANCE_OPERATOR audit event types. They read "Operator Update" and "Maintenance · Operator Update", with the icons of their TRIGGER_DEPLOY and MAINTENANCE counterparts, and show up in the Event filter.
|
View your CI Pipeline Execution ↗ for commit 286ba2e
💡 Verify your cache is correct by running tasks in a sandbox. Read docs ↗ ☁️ Nx Cloud last updated this comment at |
RemiBonnet
approved these changes
Oct 13, 2026
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## staging #3104 +/- ##
========================================
Coverage 51.51% 51.52%
========================================
Files 1382 1382
Lines 30853 30854 +1
Branches 9077 9076 -1
========================================
+ Hits 15894 15896 +2
+ Misses 12422 12421 -1
Partials 2537 2537
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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
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.
Bump qovery-typescript-axios to 1.1.1010 for the OPERATOR_UPDATE and MAINTENANCE_OPERATOR audit event types. They read "Operator Update" and "Maintenance · Operator Update", with the icons of their TRIGGER_DEPLOY and MAINTENANCE counterparts, and show up in the Event filter.
Summary
Follow-up of #3098. q-core now records Qovery Operator updates with their own audit event types instead of reusing the cluster ones:
OPERATOR_UPDATE: public route, actor is the user (wasTRIGGER_DEPLOY).MAINTENANCE_OPERATOR: Qovery admin route, actor "Qovery Agent" (wasMAINTENANCE).This PR bumps
qovery-typescript-axiosto 1.1.1010 and labels them in the audit logs:| Event | Before | After |
| --- | --- | --- |
| User Operator update |
Trigger Deploy|Operator Update(rocket icon) || Admin Operator update |
Maintenance|Maintenance · Operator Update(wrench icon)Issue:
Screenshots / Recordings
Testing
yarn testoryarn test -u(if you need to regenerate snapshots)yarn formatyarn lintPR Checklist
.cursor/rules)feat(service): add new Terraform service) - required for semantic-releaseSummary by cubic
Labels Operator update events in the audit logs. Bumps
qovery-typescript-axiosto 1.1.1010 to pick up the newOPERATOR_UPDATEandMAINTENANCE_OPERATORevent types, which q-core now records separately from cluster events.Written for commit 286ba2e. Summary will update on new commits.