Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement fedmsg meta methods in fedora messaging schema #752

Closed
Zlopez opened this issue Mar 8, 2019 · 0 comments · Fixed by #974
Closed

Implement fedmsg meta methods in fedora messaging schema #752

Zlopez opened this issue Mar 8, 2019 · 0 comments · Fixed by #974
Assignees
Labels
groomed Medium Priority This ticket has a medium priority type.feature New feature
Milestone

Comments

@Zlopez
Copy link
Contributor

Zlopez commented Mar 8, 2019

To have full functionality of fedmsg in fedora messaging, we need to implement fedmsg_meta_fedora_infrastructure methods in Anitya schema.

This will allow any application consuming Anitya messages to have the same functionality as in fedmsg.

@Zlopez Zlopez added type.feature New feature Medium Priority This ticket has a medium priority labels Mar 8, 2019
@Zlopez Zlopez added this to the 1.0 milestone Mar 16, 2020
@Zlopez Zlopez added the groomed label May 25, 2020
@Zlopez Zlopez self-assigned this Oct 8, 2020
Zlopez added a commit to Zlopez/anitya that referenced this issue Oct 8, 2020
This commit implements missing fedmsg_meta_methods. There are still few
exceptions that are not implemented.

* username - this connects to FAS which is something I don't want the
  schema to do. It shouldn't connect to any external system, this should
  be left on consumer

What is implemented:

* Anitya url for various components to have direct url in Anitya for
  these components
* List of packages in messages

Closes fedora-infra#752

Signed-off-by: Michal Konečný <[email protected]>
Zlopez added a commit that referenced this issue Oct 12, 2020
This commit implements missing fedmsg_meta_methods. There are still few
exceptions that are not implemented.

* username - this connects to FAS which is something I don't want the
  schema to do. It shouldn't connect to any external system, this should
  be left on consumer

What is implemented:

* Anitya url for various components to have direct url in Anitya for
  these components
* List of packages in messages

Closes #752

Signed-off-by: Michal Konečný <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
groomed Medium Priority This ticket has a medium priority type.feature New feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant