Open jhurliman opened 8 years ago
lambci/sources/github.js
will need a bit of tweaking for this, since Enterprise uses a single hostname for both the web frontend and the API. It follows the form https://{hostname}/api/v3/
@jhurliman interesting – is there any documentation on this? Or is the hostname literally the only difference?
It would certainly be straightforward to add this as a config param – which could be administered like the others, via the command line, etc. I'm wary of adding it to the cloudformation template just because I don't want the list of params to start blowing out – although perhaps I could just create a separate lambci-enterprise.template
that includes it.
https://developer.github.com/v3/enterprise/
Whatever works! I don't have a specific preference, just looking forward to using this.
+1 for this. We have some great use cases for this but need to use our Enterprise accounts for obvious reasons.
+1 for adding this as well. I went through the code to see where to add this and it seems it would be much easier for you to do it here as the CF template pulls the source from your s3 bucket.
Likely two useful additions would be the ability to provide the optional param here, additionally the ability to provide the S3 bucket to pull lambci code from rather than the version. Had this been there it would have been much easier for me to make the above changes. As it stands, even if I made the changes, I'll need to alter other deployment details.
Not be critical by any means, this is amazing work and super excited to use, and help out.
I hate to even ask, but with 3 years since the last bump, has the outlook on GitHub Enterprise support changed?
PRs welcome here. I don't have access to GitHub Enterprise, so it's pretty hard for me to develop for it.
This is partially, but not quite, working with GitHub Enterprise. Would love the ability to specify a GitHub Enterprise URL in the CloudFormation setup.