Skip to content
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

Rename events "ExtManagementSystem Compliance *" -> "Provider Compliance *" #13388

Merged

Conversation

cben
Copy link
Contributor

@cben cben commented Jan 8, 2017

Followup to #11002,
https://bugzilla.redhat.com/show_bug.cgi?id=1411337 (master)
https://bugzilla.redhat.com/show_bug.cgi?id=1411364 (euwe)

Before:

ems-event-missing-icons
screenshot-ems-policy

After (this PRs only fixes the event name, icons fixed in UI PR ManageIQ/manageiq-ui-classic/pull/94):

screenshot-provider-events
screenshot-provider-policy

Low-level names remain extmanagementsystem_compliance_*, should be backward compatible given existing policies with these events.

I thought this csv is loaded on every run, but it seems I needed rake db:seed to take effect.

…nce *"

Low-level names remain extmanagementsystem_compliance_*,
should be backward compatible given existing policies with these events.
@miq-bot
Copy link
Member

miq-bot commented Jan 8, 2017

Checked commit cben@36ca6ea with ruby 2.2.5, rubocop 0.37.2, and haml-lint 0.16.1
0 files checked, 0 offenses detected
Everything looks good. 🍪

@simon3z
Copy link
Contributor

simon3z commented Jan 31, 2017

@cben do you think this can be done? These are fixtures, what about existing installations out there?

@cben
Copy link
Contributor Author

cben commented Jan 31, 2017 via email

@simon3z
Copy link
Contributor

simon3z commented Jan 31, 2017

LGTM 👍

@gtanzillo do you have any insight on the backward compatibility? (It seems OK but you know more for sure)

Since this is impacting UI @h-kataria @dclarizio do you want to review/ack/nack?

Assigning to @gtanzillo for backward compatibility comments and review/merge.

@miq-bot assign gtanzillo

@dclarizio
Copy link

Since this is impacting UI @h-kataria @dclarizio do you want to review/ack/nack?

Makes sense to me!

Copy link
Member

@gmcculloug gmcculloug left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. Might want to see if there is documentation that need to be updated with this change.

@cben
Copy link
Contributor Author

cben commented Feb 7, 2017

Ping @gmcculloug so can this be merged?

This renaming itself doesn't require doc changes, but these events are missing from the list
http://manageiq.org/docs/reference/latest/doc-Policies_and_Profiles_Guide/miq/#chap_events,
I'll send a docs PR soon => ManageIQ/manageiq-documentation#223

@cben
Copy link
Contributor Author

cben commented Feb 7, 2017

These events appeared in euwe, would be nice to call the consitently there too, if there are not concerns.

@miq-bot add-label euwe/yes

@gmcculloug
Copy link
Member

Yes, I am good with merging. @gtanzillo Any concerns, if not please merge.

@gtanzillo gtanzillo added this to the Sprint 54 Ending Feb 13, 2017 milestone Feb 8, 2017
@gtanzillo
Copy link
Member

👍 LGTM

@gtanzillo gtanzillo merged commit af4f115 into ManageIQ:master Feb 8, 2017
simaishi pushed a commit that referenced this pull request Mar 3, 2017
…ption

Rename events "ExtManagementSystem Compliance *" -> "Provider Compliance *"
(cherry picked from commit af4f115)

https://bugzilla.redhat.com/show_bug.cgi?id=1411364
@simaishi
Copy link
Contributor

simaishi commented Mar 3, 2017

Euwe backport details:

$ git log -1
commit ab2c70319ea2ed076081eb948597deaccb9060a6
Author: Gregg Tanzillo <gtanzill@redhat.com>
Date:   Wed Feb 8 09:17:14 2017 -0500

    Merge pull request #13388 from cben/provider-compliance-events-description
    
    Rename events "ExtManagementSystem Compliance *" -> "Provider Compliance *"
    (cherry picked from commit af4f115902f3dfc2feec7f3c71678123c94014c6)
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1411364

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants