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.

Sign up for GitHub

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

Jump to bottom

Upgrade to Catalog Next #70

Open

jag3773 opened this issue Jun 10, 2020 · 0 comments

Assignees

Contributor

jag3773 commented Jun 10, 2020 •

edited

Loading

After Catalog Next is deployed on DCS in July, we need to make some structural changes to how the catalog works.

Stop current processor webhooks
Move source repos to their respective owners

For existing orgs, either transfer it to them, or delete the Door43-Catalog fork/copy
For groups without an org we can either
- Create an org with their name
- Use a generic org, which we will need anyway for public domain content

Update our lambda process to read from the /catalog API endpoint periodically and update the v3 endpoints if changes are detected

I think we should dockerize at least the first step of this process
Possibly dockerizing the tS v2 processor would also be warranted since it takes forever (and possibly give it access to the DB directly).

Possibly use webhooks on all repos to send Releases to the lambda function.

jag3773 assigned da1nerd

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment