-
Notifications
You must be signed in to change notification settings - Fork 392
Fix:[DI-24064] - Fix navigation for metrics and alerts under Monitor #11869
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
Fix:[DI-24064] - Fix navigation for metrics and alerts under Monitor #11869
Conversation
nikhagra-akamai
left a 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.
please add changeset
|
Coverage Report: β
|
pmakode-akamai
left a 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.
It looks like the aclpAlerting feature flag is missing in DevTools. Could we add it so we can properly test it?
Co-authored-by: Purvesh Makode <[email protected]>
@pmakode-akamai added the new feature flag - |
pmakode-akamai
left a 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.
thanks @ankita-akamai! Looks good π I've just added a comment to simplify the logic.
Cloud Manager UI test resultsπ 539 passing tests on test run #7 βοΈ
|
Description π
Hide or show 'Metrics' and 'Alerts' correctly based on all the relevant feature flags.
Changes π
Target release date ποΈ
Preview π·
here, aclp is enabled but none of the aclpalerting properties are true :
How to test π§ͺ
Verification steps
(How to verify changes)
PrimaryNav.tsx. Do hit and trial with the feature flags, making them true and false to identify all scenarios when these menu items will show/not show.Possible Scenarios:
Make use of the mocks -

Author Checklists
As an Author, to speed up the review process, I considered π€
π Doing a self review
β Our contribution guidelines
π€ Splitting feature into small PRs
β Adding a changeset
π§ͺ Providing/improving test coverage
π Removing all sensitive information from the code and PR description
π© Using a feature flag to protect the release
π£ Providing comprehensive reproduction steps
π Providing or updating our documentation
π Scheduling a pair reviewing session
π± Providing mobile support
βΏ Providing accessibility support
As an Author, before moving this PR from Draft to Open, I confirmed β