-
Notifications
You must be signed in to change notification settings - Fork 282
refactor(PZ): Replace GetTieringParameters with dogtags BED-6938 #2274
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.
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
base: main
Are you sure you want to change the base?
Conversation
WalkthroughReplaced a tiering-parameter multi-tier analysis check with the DogTags feature-flag in UpdateAssetGroupTag and wired a testable DogTags service into asset group tag tests; added a test Service implementation and overrides for dogtags. Changes
Sequence Diagram(s)(omitted) Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested labels
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 1 | ❌ 2❌ Failed checks (2 warnings)
✅ Passed checks (1 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches
Comment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@cmd/api/src/services/dogtags/service.go`:
- Around line 39-83: testService.GetAllDogTags currently only adds bool and int
tags; update it to also iterate AllStringDogTags and add those entries using
s.GetFlagAsString(key) so testService mirrors the production service; locate the
method testService.GetAllDogTags and append a loop over AllStringDogTags that
sets result[string(key)] = s.GetFlagAsString(key).
- Add NewTestService helper for configurable test overrides - Update UpdateAssetGroupTag to use DogTags.GetFlagAsBool - Update tests to use NewTestService with appropriate overrides
b80b60b to
92020b1
Compare
Description
Describe your changes in detail
Motivation and Context
Resolves <TICKET_OR_ISSUE_NUMBER>
Why is this change required? What problem does it solve?
How Has This Been Tested?
Please describe in detail how you tested your changes.
Include details of your testing environment, and the tests you ran to
see how your change affects other areas of the code, etc.
Screenshots (optional):
Types of changes
Checklist:
Summary by CodeRabbit
Refactor
Tests
✏️ Tip: You can customize this high-level summary in your review settings.