sinnykumari added a new comment to an issue you are following:
``
What if the fedmsg just linked to the compose? Then each caller
would parse the existing compose metadata JSON, and we wouldn't need to define a new
schema.
Did you mean that
[
fedmsg](https://apps.fedoraproject.org/datagrepper/raw?topic=org.fedorapr...
published by atomic two week release script should only contain link to compose and then
callers like fedora-website fetches json from the compose url? Something like -
```
"msg" {
"url":
"/pub/alt/atomic/stable/Fedora-Atomic-28-20180515.1/metadata"
}
```
Technically it is possible that callers can fetch json data from the url link. One
drawback I see with this approach is callers will also have to be aware of any changes
made in compose metadata json schema. On the other hand, if all relevant information is
provided by twoweek fedmsg, then caller will have to only look for changes made in fedmsg
content.
Also, I hope that this new schema change will be only one time to accommodate multi-arch
information. Sadly, I don't see a possible way to extend existing two week fedmsg
schema with multi-arch content without breaking compatibility with older schema.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/392