Nasar Khan
Nasar Khan
- picking up and continuing from https://github.com/ManageIQ/manageiq/pull/21361 - set Kafka as the default messaging_type for events i.e. ``` nasarkhan@Nasars-MacBook-Pro manageiq % kafka-console-consumer --bootstrap-server localhost:9092 --topic manageiq.ems --from-beginning {"event_type":"test_action","source":"IBMCloud-VPC","username":"nasar123","ems_id":1,"ems_ref":"abc","timestamp":"1234","vm_uid_ems":"vm","vm_ems_ref":"vm_ref"} {"ems_ref":"event-ref","ems_id":34000000000941,"event_type":"STUFF_HAPPENED"} ```...
- systemd file needed for the addition of `manageiq-messaging-ready` script Depends on: - [ ] https://github.com/ManageIQ/manageiq-appliance/pull/368 @miq-bot add_label enhancement @miq-bot assign @agrare
Improved resources/info reported in `managed_resources` function, which will be used for further data reporting in the future @miq-bot assign @Fryguy @miq-bot add_reviewer @Fryguy @miq-bot add_label enhancement
- mount the necessary messaging configs from their respective secrets using a projected volume mount Depends on: - [ ] https://github.com/ManageIQ/manageiq-pods/pull/1041 @miq-bot assign @bdunne @miq-bot add_reviewer @Fryguy @miq-bot add_label enhancement,...
Currently if util functions are needed elsewhere, the entire `miq-components` package needs to be pulled. It would be nice to be able to pull in just the util methods, this...
- move messaging config from env vars to file - the configs will be stored in secrets and mounted as a projected volume since the kafka user password is located...
We no longer use a push/pop approach as health check for kafka via the orchestrator and so this topic no longer needs to be created Ref: https://github.com/ManageIQ/manageiq/pull/23020 @miq-bot assign @bdunne...