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
Hide Driving Event field for Containers. #4324
Hide Driving Event field for Containers. #4324
Conversation
f67be24
to
67d21a0
Compare
@lgalis please review/test |
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.
Looks good. Verified that the Driving Event is not displayed for Containers but displayed for the other alret types.
67d21a0
to
1879d29
Compare
@h-kataria Could you please address the rubocop warnings in the spec? Thanks. |
1879d29
to
c4dd02b
Compare
As per https://bugzilla.redhat.com/show_bug.cgi?id=1578115#c26 in BZ removed an option to be able to set/display 'Driving Event' field when adding/editing an Alert that's based on 'Container Node' or 'Container Project' models. Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1578115
c4dd02b
to
6b57930
Compare
Checked commit h-kataria@6b57930 with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0 **
|
…aiers Hide Driving Event field for Containers. (cherry picked from commit 6b0c400) Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1607438
Gaprindashvili backport details:
|
As per https://bugzilla.redhat.com/show_bug.cgi?id=1578115#c26 in BZ removed an option to be able to set/display 'Driving Event' field when adding/editing an Alert that's based on 'Container Node' or 'Container Project' models.
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1578115
before:
after: