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

Update GitHub gateway to new GitHub app #746

Closed
4 tasks done
radu-matei opened this issue Jan 4, 2019 · 5 comments
Closed
4 tasks done

Update GitHub gateway to new GitHub app #746

radu-matei opened this issue Jan 4, 2019 · 5 comments
Assignees
Projects

Comments

@radu-matei
Copy link
Contributor

radu-matei commented Jan 4, 2019

This issue tracks the progress towards migrating to the new Brigade GitHub App:

  • Disable GH gateway by default
  • Add GitHub App support to the Github Gateway
  • Add check_suite support to the Github Gateway
  • Delete the github.com/Azure/brigade-github-app (that will be replaced by this) edit (vdice): we've decided to keep this gateway in the form of a separate repo and chart

related: #407, #225, #318

@radu-matei radu-matei added the v1.0 label Jan 4, 2019
@technosophos technosophos mentioned this issue Jan 4, 2019
19 tasks
@radu-matei radu-matei added this to To do in Brigade Jan 4, 2019
@vdice
Copy link
Contributor

vdice commented Feb 5, 2019

I started circling around this today, re-familiarizing myself with brigade-github-app and what it would look like to swap out Brigade's current/classic github gateway with the former.

However, before getting into the details of what this may look like -- though, I will mention, it might just look like removing brigade's current gh-related files in pkg/webhook and swapping in those from brigade-github-app, as well as updating brigade-github-gateway/cmd similarly) -- I wanted to propse the following:

If the intention is to disable the GH gateway by default, as is the first bullet above, why not continue to host this (perhaps updated) gateway in Azure/brigade-github-app as well as continue to keep its separate Helm chart as exists today and just remove all GH gateway code from this repo itself? Then, enabling becomes a matter of flipping a chart flag and thus including the brigade-github-app sub-chart into the release. This would contribute to a more modular/composable Brigade setup, which seems to be a preferred way forward.

Thoughts?

@radu-matei
Copy link
Contributor Author

Sure, that makes sense - however, would it make sense to migrate it over to brigadecore?

@vdice
Copy link
Contributor

vdice commented Feb 5, 2019

Yes, definitely -- assuming here all Brigade-related repos would migrate to brigadecore.

@vdice
Copy link
Contributor

vdice commented Feb 5, 2019

Pull requests are up with strategy mentioned above (remove older github gateway code/chart resources from Brigade in favor of opt-in approach to conditionally use brigade-github-app code/chart):

#797
Azure/brigade-charts#22

PTAL @radu-matei @adamreese @technosophos

@vdice vdice moved this from In progress to Needs review in Brigade Feb 7, 2019
@vdice
Copy link
Contributor

vdice commented Feb 12, 2019

Both aforementioned PRs merged; closing.

@vdice vdice closed this as completed Feb 12, 2019
Brigade automation moved this from Needs review to Done Feb 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Brigade
  
Done
Development

No branches or pull requests

2 participants