dustymabe added a new comment to an issue you are following:
One drawback I see with this approach is callers will also have to be aware of any
changes made in compose metadata json schema.
But we should probably be avoiding breaking that anyways, right?
I guess my strawman proposal here is that we keep the existing fedmsg schema, just add a
new key msg/url key like you suggested, and teach websites to parse the compose data.
Makes sense and I have no objection with this.
To decide which option to choose, I am interested in knowing if we have any existing
fedmsg as example which just pass url and callers do processing?
Also @dustymabe and @mohanboddu what are your opinion here?
whatever works for me. It would be interesting to know if there were any other consumers
of this fedmsg other than the website. none that I know of.
To reply, visit the link below or just reply to this email