-
Notifications
You must be signed in to change notification settings - Fork 202
Allow generating service without a route #1209
Comments
Hey @chmouel You need to do some little changes in pom.xml and probably it should work.
Can you please try this configuration. Please let us know if this doesn't resolve your problem. Thanks |
Hi @chmouel, The file you are showing is the resource file which is getting generated. When you hit fabric8: resource, it generates :
The above configuration I provided will generate all the resource yaml, no change in that behavior but I will not create a route resource on your OpenShift cluster when you hit fabric8: deploy goal. If you hit fabric8: deploy goal without this configuration it will generate a route on your cluster. Above configuration is wrt to resources on the cluster, not the yaml. I think this will resolve your problem. Let us know if you have some other doubt. Thanks |
Even making https://github.com/fabric8-services/fabric8-tenant-jenkins/blob/master/apps/content-repository/src/main/fabric8/content-repository-svc.yml#L14 to The requirement here is |
fabric8.openshift.generateRoute which of set to false no route.yaml will be generated and if set true or not set it will generate route.yml fabric8io#1209
As #1211 is merged, I am closing this. |
Currently when generating a service with f-m-p it would generate a Route along the way which is not needed, it would be useful to have a flag so it the Route doesn't get generated along the Service.
The text was updated successfully, but these errors were encountered: