[release] fedora-messaging-1.6.0

[Jeremy Cline]

Hey folks,

Earlier last week I tagged 1.6.0 of fedora-messaging; the release notes
are in the docs[1].

There is also documentation on connecting to Fedora's message broker
externally. I would be very grateful if interested folks could run
through the documentation[2] and let me know if they hit any snags or
if anything was confusing. If you're not up and running in two minutes,
there's a problem with the documentation.

fedora-messaging-1.6.0 is available on PyPI, in Rawhide, and in updates-
tesing for Fedora 29 and 30. It's also available in the infra repos for
Fedora 28 and EPEL7.

[1] 
https://fedora-messaging.readthedocs.io/en/stable/changelog.html#v1-6-0-2...
[2] https://fedora-messaging.readthedocs.io/en/latest/fedora-broker.html


Regards,
Jeremy

[Kevin Fenzi]

On 4/6/19 9:08 AM, Jeremy Cline wrote:
>  Hey folks,
>  
>  Earlier last week I tagged 1.6.0 of fedora-messaging; the release notes
>  are in the docs[1]. 
Awesome. Thanks for all the work on it.

>  There is also documentation on connecting to Fedora's message
> broker
>  externally. I would be very grateful if interested folks could run
>  through the documentation[2] and let me know if they hit any snags or
>  if anything was confusing. If you're not up and running in two minutes,
>  there's a problem with the documentation. 
Worked fine here. ;)

Are there any plans to have something like fedmsg-tail and
fedmsg-trigger? those are both quite useful. Also, is there any chance
for something like fedmsg's '--terse' output? ie, one line condensed
version of the message?

kevin

[Jeremy Cline]

On 4/7/19 1:49 PM, Kevin Fenzi wrote:
>  On 4/6/19 9:08 AM, Jeremy Cline wrote:
> > Hey folks,
> >
> > Earlier last week I tagged 1.6.0 of fedora-messaging; the release notes
> > are in the docs[1].
>  
>  Awesome. Thanks for all the work on it.
>  
> > There is also documentation on connecting to Fedora's message broker
> > externally. I would be very grateful if interested folks could run
> > through the documentation[2] and let me know if they hit any snags or
> > if anything was confusing. If you're not up and running in two minutes,
> > there's a problem with the documentation.
>  
>  Worked fine here. ;) 
Great, thanks for giving it a try.

>  
>  Are there any plans to have something like fedmsg-tail and
>  fedmsg-trigger? those are both quite useful. Also, is there any chance
>  for something like fedmsg's '--terse' output? ie, one line condensed
>  version of the message? 
I don't have any specific plans, but those should all be very easy to 
implement as consumer functions. In the demo config, it's just using
the "fedora_messaging.example:printer" callback which is basically just:

def printer(message):
     print(message)

so there's definitely room for fancier "printer-like" callbacks. For
that and other general callbacks (like executing some command), we could
certainly include and document them in fedora-messaging.

Could you file an issue[0] and cover the things you currently do or
would *like* to do? Re-implementing the functionality of those commands
in fedora-messaging is fine, but it wouldn't hurt to incorporate
any obvious improvements while we're at it.

[0] https://github.com/fedora-infra/fedora-messaging/issues

- Jeremy

[Kevin Fenzi]

On 4/8/19 7:28 AM, Jeremy Cline wrote:

>  
>  Could you file an issue[0] and cover the things you currently do or
>  would *like* to do? Re-implementing the functionality of those commands
>  in fedora-messaging is fine, but it wouldn't hurt to incorporate
>  any obvious improvements while we're at it. 
Sure! done.

https://github.com/fedora-infra/fedora-messaging/issues/155
https://github.com/fedora-infra/fedora-messaging/issues/156

kevin