Enable server-push using ActionCable

[skateman]

This PR enables server-push in ManageIQ using ActionCable. The plan is to use it for asynchronous notifications displayed in the form of PatternFly toasts. This PR just implements a PoC solution, where the notifications are logged into the browser's JS console.

For testing it is necessary to run run cp config/cable.yml.sample config/cable.yml or re-run bin/setup. Then log in to the Web UI and open the browser's JavaScript console. Notifications can be emitted using a rails console in the following form:

ActionCable.server.broadcast("notifications_#{user_id}", message)

Where user_id is the numerical database ID of the logged in user and the message is an instance of a Hash object.

[isimluk]

Ack. from backend perspective.

[himdel]

aah, can you do this in a separate .then? Because now failures from ws_init would be ignored..

[skateman]

@himdel check it out now

[himdel]

var miqInitNotifications = function () { or function miqInitNotifications() { please :)

[himdel]

Feels wrong to add something quite unrelated to API code since there's no real direct dependency.

Can you rewert the autorenew -> init change please and just call miqInitNotifications in application.html.haml?

Or move this init function outside the API code.

[miq-bot]

Checked commits skateman/manageiq@bd94c54~...ced4ed3 with ruby 2.2.5, rubocop 0.37.2, and haml-lint 0.16.1
8 files checked, 1 offense detected

app/channels/application_cable/connection.rb

• ⚠️ - Line 14, Col 23 - Lint/AssignmentInCondition - Assignment in condition - you probably meant to use ==.

[skateman]

@himdel fixed, @miq-bot remove_label wip