]
Fred Bricon reassigned JBIDE-20546:
-----------------------------------
Assignee: Jeff Cantrill
[~jcantrill] you mentioned the possibility of getting the webhook using a different
method, so I'll let you investigate for CR1, if possible
Discrepancy between git webhooks shown in OpenShift tooling vs Web
Console
--------------------------------------------------------------------------
Key: JBIDE-20546
URL:
https://issues.jboss.org/browse/JBIDE-20546
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.0.CR1
Reporter: Fred Bricon
Assignee: Jeff Cantrill
Fix For: 4.3.0.CR1
Bug initially reported as
https://github.com/openshift/origin/issues/4458. Duplicating
here for documentation purposes.
{quote}
Creating apps on a bunch of servers running OS3 v1, I noticed the webhooks the web
console shows are of the form:
https://api.xxx.openshift.com/osapi/v1beta3/namespaces/ks/buildconfigs/ea...
The java rest client @jcantrill is working on generates urls following the actual OS
version, i.e:
https://console.xxx.openshift.com/oapi/v1/namespaces/ks/buildconfigs/eap-...
Turns out only the v1beta3 url work. Still, this seems unexpected. So the question is:
should openshift servers use a v1 based webhook url or
should the java rest client be "fixed" to use v1beta3 urls instead of v1 when
computing webhooks?
{quote}