Using its own BuildConfig when using f-m-p

Is it a way to define its own BuildConfig when using f-m-p (like adding a bc.yml file in src/main/fabric8) ?

Description

Got my BuildConfig always overridden by fabric8 plugin and would really like to tune it and use it

Info

• f-m-p version : v3.5.31
• Maven version (mvn -v) : 3.3.9
• Kubernetes / OpenShift setup and version : openshift v1.5.1 kubernetes v1.5.2+43a9be4
• If it’s a bug, how to reproduce : having this kind of file in src/main/fabric8:

apiVersion: v1
kind: BuildConfig
metadata:
  name: mybuildconfig
  namespace: projectname
spec:
  source:
    binary: {}
    type: Binary
  output:
    pushSecret:
      name: artifactory
    to:
      kind: ImageStream
      name: myimagestream
  strategy:
    dockerStrategy: {}
    type: Docker
  triggers:
  - generic:
      secret: dummysecret
    type: Generic
  nodeSelector:
    kubernetes.io/hostname: hostname

It gets overridden when executing mvn fabric8:build with especially annoying removal of pushSecret because of this: https://github.com/fabric8io/fabric8-maven-plugin/blob/9102af60e232c1ac6e2cc29d81ffd8f13f562bab/core/src/main/java/io/fabric8/maven/core/service/openshift/OpenshiftBuildService.java#L179-L182

Thank you in advance for your kind help

[rhuss]

@zonArt no, not yet. But we are currently reworking the whole build part to allow for a more flexible way of building images. This also affects the s2i build part, and when redoing this we should add the corresponding s2i config hooks.

What’s your actual use case or better, what do you want to be configurable in the build config / imagestream ?

[stale[bot]]

This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!