You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's Release bot as Github App, but it's currently not running because we lack resources on Openshift Online, where the bot is deployed.
For the Github App to be able to talk to the service (the deployed bot) the service url needs to be publicly available which rules out most of our internal Openshift clusters.
Today I woke up and got an idea that we could possibly work-around it with ngrok.
Not sure it'd work, but worth trying.
The thing is that AFAIK one has to have paid account to use custom subdomains, so we'd probably need to run the ngrok in the same pod as the release-bot - which already is quite stuffed.
Just noticed this..I this still something you want to pursue? We also have ultrahook running internally which is super simple to setup https://github.com/AICoE/ultrahook-openshift/
There's Release bot as Github App, but it's currently not running because we lack resources on Openshift Online, where the bot is deployed.
For the Github App to be able to talk to the service (the deployed bot) the service url needs to be publicly available which rules out most of our internal Openshift clusters.
Today I woke up and got an idea that we could possibly work-around it with ngrok.
Not sure it'd work, but worth trying.
The thing is that AFAIK one has to have paid account to use custom subdomains, so we'd probably need to run the ngrok in the same pod as the release-bot - which already is quite stuffed.
I've also found @vpavlin's https://github.com/vpavlin/ngrok-openshift which we could borrow some bits from ;-)
The text was updated successfully, but these errors were encountered: