On Thu, Feb 25, 2016 at 7:08 PM, Jordan Liggitt <[email protected]> wrote:
> The UI can certainly do that (it already has file inputs in other forms). > A presentation hint would be helpful for the template author to be able to > express (text field, multi-line textbox, or file input)... it would look > awful for every field to have a "single/multi/file" toggle beside it. > Agreed, I wouldn't want to have a file input showing up on every parameter input. > > On Thu, Feb 25, 2016 at 6:10 PM, Ben Parees <[email protected]> wrote: > >> I wouldn't expect the template format itself to support a file reference, >> but having the UI support some sort of "upload from file" option for >> filling in a parameter value seems more likely (though still not super >> likely). Will leave it to the UI team to comment on the likelihood of such >> a feature. >> >> (I would have similar expectations regarding having the template >> instantiation CLI support supplying a parameter value from a local file) >> >> >> On Thu, Feb 25, 2016 at 5:35 PM, Philippe Lafoucrière < >> [email protected]> wrote: >> >>> Hi Guys, >>> >>> I wonder if having a file parameter in template would be added to the >>> roadmap. >>> My point: a deployer template where I can pass directly certificates and >>> keys as files. The main difference would be in the UI, where the field >>> would be a file input, instead a text input. >>> >>> Thanks, >>> Philippe >>> >>> _______________________________________________ >>> dev mailing list >>> [email protected] >>> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev >>> >>> >> >> >> -- >> Ben Parees | OpenShift >> >> >> _______________________________________________ >> dev mailing list >> [email protected] >> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev >> >> >
_______________________________________________ dev mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
