This PR enables users to specify whether they want to allow insecure connections to the Gitea instance.
This becomes important when a user has started a Gitea server in a cluster and they are trying to create an application from one of the repositories of the Gitea server in the same cluster.
The issue that is observed in this case is the build is failing as git clone command is not able to access the repository URL as by default all insecure connections are blocked.
One of the solutions is to install proper SSL certificates, but its complicated for simple development practises.
P.S. I am from the Openshift Developer Console UI Team. Currently, we are implementing Gitea as one of the Git Providers into the "Import Forms". We are using this helm chart to install Gitea on the cluster for development. This update would help me in the process.
How do we test this?
Install the helm chart with the allowInsecure set to "Allow"
Now you can reach the gitea server even from insecure connections
What is this PR About?
This PR enables users to specify whether they want to allow insecure connections to the Gitea instance. This becomes important when a user has started a Gitea server in a cluster and they are trying to create an application from one of the repositories of the Gitea server in the same cluster. The issue that is observed in this case is the build is failing as
git clone
command is not able to access the repository URL as by default all insecure connections are blocked. One of the solutions is to install proper SSL certificates, but its complicated for simple development practises.P.S. I am from the Openshift Developer Console UI Team. Currently, we are implementing Gitea as one of the Git Providers into the "Import Forms". We are using this helm chart to install Gitea on the cluster for development. This update would help me in the process.
How do we test this?
cc: @redhat-cop/day-in-the-life