A template is a list of "any object". So the things you put as items in the objects array are the things you would "oc explain deployment|service|secret|*" on
On Wed, Mar 6, 2019 at 12:16 PM Just Marvin < marvin.the.cynical.ro...@gmail.com> wrote: > Clayton, > > Appreciate the quick response. Is there an alternative for getting > information on the structure of a template? Most of the interesting content > in a template is under that "objects" tree. For example, > template.objects.spec doesn't work either. I tried "oc explain object" but > the tool wasn't too happy about that. > > Regards, > Marvin > > On Wed, Mar 6, 2019 at 11:53 AM Clayton Coleman <ccole...@redhat.com> > wrote: > >> Objects is opaque (literally "any object") so you can't get open api >> metadata on it. >> >> On Wed, Mar 6, 2019 at 11:51 AM Kenneth Stephen < >> marvin.the.cynical.ro...@gmail.com> wrote: >> >>> Hi, >>> >>> The structure of a template is <document root> --> objects --> >>> metadata . "oc explain template.objects" shows me good results, though the >>> output of it doesn't show a metadata child. "oc explain >>> template.objects.metadata" fails saying "error: field "metadata" does not >>> exist". What is the right syntax for dealing with the "objects" array? >>> >>> Thanks, >>> Marvin >>> _______________________________________________ >>> users mailing list >>> users@lists.openshift.redhat.com >>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users >>> >>
_______________________________________________ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
