title: How to inject a configuration file into an openshift docker build (not a pod)
body: <p>Before the docker build starts I am producing a configuration file which contains a lot of environment specific configuration. I don't want it in my repository because it changes frequently.</p>
  
  <p>Openshift recommends for artifacts needed during a docker build to downloaded them directly from the container. <a href="https://docs.openshift.com/container-platform/3.4/dev_guide/builds/build_inputs.html#using-external-artifacts" rel="nofollow noreferrer">Here</a>. Since they are mostly unique for each deployment and immutably stored on the container I would like to avoid having to first push the config file to a artifact repo just to download it again from the container.</p>
  
  <p>Additionally they may have sensitive data. (although that should be easy to inject via environment variables)  </p>
  
  <p>Is there a different way to pass small configuration files (&lt;10KB) to the openshift docker build context?</p>
  
  <p>Update: I only use openshift in this case as a docker builder and push the target to an external repository. From there the container is picked up for deployment.
  (The situation is we are in the middle of a migration where the target architecture is not yet defined, but some specific parts must be already used. Like Openshift for cicd) </p>