-
Notifications
You must be signed in to change notification settings - Fork 357
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
Enable MW Compliance and Control policies #2436
Conversation
@miq-bot add_label enhancement, middlaware |
@karelhala Cannot apply the following label because they are not recognized: middlaware |
@miq-bot add_label middleware |
ce523fc
to
45d9c1a
Compare
@miq-bot add_label control |
@jdoyleoss @Loicavenel I'd like to make sure - is this how you envision this feature in regards to EAP? that it's a sub category under middleware servers? (not saying it is incorrect, would like to verify with you that was the intention) |
@abonas all should be done, this enables MW policies in control panel, but no button inside server to assign policies to specific entities. Because if I understand assigning of policies correctly if you were to add policy on Provider level, you will also assign such policy for all it's servers (which is OK) and all server's items (datasources, deployments and such) - might not be OK. But I might be mistaken @Loicavenel is this correct? |
@karelhala I think you misunderstood my question, but the above also is an important thing to verify:
|
Based on the screenshots, this is what we discussed before and this will work. 1 - Everything is an EAP Server and this is a parameter that identify the Type: Fuse, DataVirt etc.. |
don't know what DataVirt is, but not everything is an EAP server.
probably a more correct approach |
Please proceed as shown in the screenshots. This is what was agreed in the
JIRA.
We are breaking out the different middleware servers as different types, so
I expect that we will make distinction based upon that once we get Fuse and
others in.
~john
…On Thu, Oct 26, 2017 at 1:50 PM, abonas ***@***.***> wrote:
Based on the screenshots, this is what we discussed before and this will
work.
What we discussed few times and I am not sure if you will implement it in
the future is the Middleware Modeling:
1 - Everything is an EAP Server and this is a parameter that identify the
Type: Fuse, DataVirt etc..
don't know what DataVirt is, but not everything is an EAP server.
and Fuse != EAP. @jdoyleoss <https://github.com/jdoyleoss> please confirm
2 - There is one Object per Type: Fuse, DataVirt etc...
probably a more correct approach
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2436 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAfbZSZHUKiXRhQDmAPcMHOkLsNQUxYHks5swMaCgaJpZM4P9ScI>
.
|
@miq-bot assign @martinpovolny |
@miq-bot assign @gtanzillo |
This pull request is not mergeable. Please rebase and repush. |
@karelhala this needs a rebase and repush |
@aljesusg please review this as well |
Failing travis is not problem of this PR. |
Checked commit karelhala@9b41315 with ruby 2.3.3, rubocop 0.47.1, and haml-lint 0.20.0 |
@miq-bot assign @h-kataria |
@martinpovolny or @h-kataria can you merge this? Travis error is not related. |
@miq-bot assign @martinpovolny |
merging, Travis failures are unrelated to changes here. |
Introduces new menu item in Policies
Middleware provider needs to set up Compliance and Control policies. Base model is MW server, to create policy for EAP we have to cewate policy with scope somehow set to EAP.