If you take a look at the document using Probot to implement the GitHub App manifest flow, you can see how to create a GitHub App Manifest using Probot. And I know that Probot can be used with GitHub Enterprise. So, I suspect this can be done with a couple extra steps, but I don't know of a single-click App-to-Enterprise manifest system currently.
I hope that helps!
I have been spending quite some time to get some useful info on how our users would install a (probot based) github app that would work with with the GitHub Enterprise (server) that my team is responsible for. And all the links go to https://github.com/probot/probot/issues/500 which then points to https://probot.github.io/docs/deployment/ but in my opinion it does not really answer the question especially because we need something that works within our firewalls.
All that we are looking for is some steps or suggestion on setting things up. I want to tell the users of our installation that if you want to use a probot based github app, then need to do\have ........ but I don't have an answer. At this moment I don't even know if we, as the owner of the GitHub Enterprise installation need to do something to accomodate this.
Of course I can reach out to GitHub support but I believe that this is info that should be easily available for GitHub Enterprise Server users.
Thanks for sharing this information and your feedback. I can understand why that would be valuable. However, given the inevitable variance that occurs across different organization's internal IT infrastructure, it would be very difficult to provide documentation that achieves what you're asking for and is applicable to all organizations. This is more of a specific instance question, and I actually would recommend reaching out to GitHub Enterprise Support for help.
Please let me know if you have any other questions.
Mark helpful posts with Accept as Solution to help other users locate important info. Don't forget to give Kudos for great content!
However, given the inevitable variance that occurs across different organization's internal IT infrastructure, it would be very difficult to provide documentation that achieves what you're asking for and is applicable to all organizations. This is more of a specific instance question, and I actually would recommend reaching out to GitHub Enterprise Support for help.
I disagree. Implementing the "GitHub App from manifest workflow" in GitHub Enterprise as it is implemented in GitHub.com is not specific to any instance. It is just a shortcut for the user of GitHub Enterprise to not having to fill in the "Create new GitHub App" form manually when integrating with software that provides a GitHub App. It has nothing to do with the organization's internal IT infrastructure.
The question that @braeken asked was specifically referencing the Probot deployment documentation and how to achieve that inside their organization's firewalls. How to deploy something within any given organization's firewalls has everything to do with that organization's IT infrastructure and isn't something that we can answer.
Just wanted to add that app manifests are a fairly new feature, so this flow became available on the most recent release of GitHub Enterprise (2.16). Previous to 2.16 you have to create the GitHub App manually. Once you add all the environment variables (App ID & Private Key), Probot will effectively "skip" the manifest setup option.