Migrate 'packit/deployment' to 'Webhook To Fedora Messaging'

[gridhead]

This project was listed in the GitHub2FedMsg database and we want to you to inform you about the upcoming deprecation of the service. As the Fedora Infrastructure is finishing up with migrating its applications away from FedMsg to Fedora Messaging, we encourage you to migrate your repository to the successor of the GitHub2FedMsg project, Webhook To Fedora Messaging.

Please follow this link to the official announcement of the project’s release and use the instructions there to migrate to the new service. If this notification was a mistake, please close this notification ticket. We will not act on the repositories whose migrations have not been requested and any related GitHub2FedMsg operations will stop working once the service is decommissioned.

[mfocko]

I'll reply here as it makes sense to me to keep the track in this repo and close the others as subtasks…

If I wish to skip the whole bureaucratic process of migrating via the ticket (we're talking about removal of one app, and configuring a webhook (to which you don't have permissions anyways…)) I should do the following:

• [x] Log in here
  • I kinda wonder why the Swagger API hides behind the /docs endpoint, that feels like a very weird choice to me, but let's move on
• [x] Create a service
  • I guess name=packit, type=github, desc=‹insert happy story› is fine?
  • if I want to enable it at the org-level, one should be enough, right?
• [x] Use the token and webhook URL from the response to configure it org-wide

Did I get it right?

---

OTOH I don't really like the fact I had to search for that repo on the GitHub anyways, cause there's no link from the API nor any docs I've managed to find at the first look.

Also the docs didn't help much :/

[abompard]

Yes, you got that right. We've opened a tracker because the login process via Swagger UI isn't very well streamlined, but if you prefer doing it directly then yeah please do! :-)

[mfocko]

Yes, you got that right. We've opened a tracker because the login process via Swagger UI isn't very well streamlined, but if you prefer doing it directly then yeah please do! :-)

Thanks a lot, appears to be done, got 202 back from the initial ping :tada:

Closes packit/rpm-shim#19 Closes packit/helm#31 Closes packit/configuration-migrations#2 Closes packit/contributing#40 Closes packit/status#168 Closes packit/prepare-release#32 Closes packit/agile#673 Closes packit/research#218 Closes packit/actions#20 Closes packit/specfile#422 Closes packit/dist-git-to-source-git#248 Closes packit/upsint#66 Closes packit/sandcastle#211 Closes packit/requre#289 Closes packit/pre-commit-hooks#46 Closes packit/packit-service-fedmsg#116 Closes packit/packit-service#2618 Closes packit/packit.dev#965 Closes packit/packit#2459 Closes packit/ogr#870 Closes packit/dashboard#479