hello all
start to set the s2i to build the image and ,set the token in this process. and we see it just add the path url in the remote webhook url.as below:
http://s2ioperator-trigger-service.kubesphere-devops-system.svc:8081/s2itrigger/v1alpha1/general/namespaces/gitlab/s2ibuilders/s21-python-latest-jpx/?secretCode=123456789
and in the gitlab we also find in the webhook , it also has the secret token in the page
however , maybe it not same function . gitlab will put the secret in the X-Gitlab-Token HTTP header. not in the url path 。
so , if it will be update to match the gitlab secret token function .
use the token in the process. it just put the token in the url and gitlab also need to add the full url in the webhook with token .
it‘not different without token.
hello all
start to set the s2i to build the image and ,set the token in this process. and we see it just add the path url in the remote webhook url.as below:
http://s2ioperator-trigger-service.kubesphere-devops-system.svc:8081/s2itrigger/v1alpha1/general/namespaces/gitlab/s2ibuilders/s21-python-latest-jpx/?secretCode=123456789
and in the gitlab we also find in the webhook , it also has the secret token in the page
however , maybe it not same function . gitlab will put the secret in the X-Gitlab-Token HTTP header. not in the url path 。
so , if it will be update to match the gitlab secret token function .
use the token in the process. it just put the token in the url and gitlab also need to add the full url in the webhook with token .
it‘not different without token.