Hide Forgot
What is the nature and description of the request? As a user of OpenShift I want to have the ability to nest environment variables so that I can keep the existing variables provided by OpenShift and expand them or use them in conjunction with other variables. Why does the Business need this? (List the business requirements here) This is needed to allow for simpler and less upfront knowledge of what is stored in variables. It also removes the need to build images with variables pre-defined. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. Functionally the only requirement is that when a docker build is done, 1 ENV statement can process variables defined in the same line. Unlike what is seen in https://gist.github.com/bparees/daf9c6ecbd87b4ea61f233d7474411d3
Would it be better to simply provide customer with information related to https://docs.openshift.com/enterprise/3.2/dev_guide/configmaps.html However this would not work for builds.
I think you answered your own question. It depends on the customer's use case but this seemed like a build specific request.