On Tue, Jul 3, 2018 at 12:56 PM, Andrew Feller <afel...@bandwidth.com> wrote:
> I see there is a way to escape environment variable references > <https://docs.openshift.com/container-platform/3.6/dev_guide/downward_api.html#dapi-escaping-environment-variable-references>, > however I wanted to see if there was a way to escape OpenShift template > parameter references as I wanted to pass Jenkins environment variable > references to BuildConfig SCM attributes to be evaluated later in a way > that someone couldn't break them by declaring an OpenShift template > parameter of the same name. Looking at the oc process logic > <https://github.com/openshift/origin/blob/master/pkg/template/templateprocessing/template.go>, > it doesn't appear this is supported but thought would ask. > no i'm afraid not. You could forestall such problems by defining a parameter with a default value that is the env reference, though. > Thanks! > > -- > > [image: BandwidthMaroon.png] > > Andy Feller • Sr DevOps Engineer > > 900 Main Campus Drive, Suite 500, Raleigh, NC 27606 > > > e: afel...@bandwidth.com > > _______________________________________________ > users mailing list > users@lists.openshift.redhat.com > http://lists.openshift.redhat.com/openshiftmm/listinfo/users > > -- Ben Parees | OpenShift
_______________________________________________ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
