TKN-TRIGGERTEMPLATE-DESCRIBE(1)
π tkn-triggertemplate-describe β bestie edition β¨
okay so real quick, this page is TKN-TRIGGERTEMPLATE-DESCRIBE(1) β the whole manual β and it's literally about one thing: describing a TriggerTemplate. in a namespace. that's the vibe. π
πΈ NAME πΈ
tkn-triggertemplate-describe β Describes a TriggerTemplate in a namespace π
β¨ SYNOPSIS β¨
tkn triggertemplate describe
that's it. that's the whole entry point. icon behavior honestly π«Ά
π¦ DESCRIPTION π¦
so like β it Describes a TriggerTemplate in a namespace. no cap, that's the entire job description. it's giving "tell me everything about this TriggerTemplate" main character energy π
π OPTIONS π
here's where it gets juicy, bestie. every single flag, zero skips:
--allow-missing-template-keys[=true]β if this is true, it just β¨ ignoresβ¨ any errors in templates when a field or map key is missing in the template. ngl it's forgiving like that. only applies to golang and jsonpath output formats though, so don't get too comfy π-h,--help[=false]β help fordescribe. your little "wait what does this do again" button π«Ά-o,--output=""β output format. must be one of:json,yaml,name,go-template,go-template-file,template,templatefile,jsonpath,jsonpath-as-json,jsonpath-file. pick your fighter π--show-managed-fields[=false]β if true, it keeps themanagedFieldswhen printing objects inJSONorYAMLformat. default is off, so the fields stay hidden unless you ask π--template=""β a template string or a path to a template file, used when you're doing-o=go-templateor-o=go-template-file. the template format is golang templates [ β¨http://golang.org/pkg/text/template/#pkg-overviewβ© ] β yes that's the real link, copy it exactly, i don't make the rules π§
π OPTIONS INHERITED FROM PARENT COMMANDS π
these ones come from the parent command, so they're like... family. inherited. nepo flags, if you will π
-c,--context=""β name of the kubeconfig context to use (default:kubectl config current-context) β so if you don't say anything, it peeks at your current context π-k,--kubeconfig=""β kubectl config file (default:$HOME/.kube/config) β the classic, the standard, the blueprint π-n,--namespace=""β namespace to use (default: from$KUBECONFIG) β leave it blank and it'll pull the namespace out of yourKUBECONFIGfor you β¨-C,--no-color[=false]β disable coloring (default:false). so like, colors are ON by default, and this flag is the "please, i'm in a plain terminal" escape hatch π
β EXAMPLE β
describe a TriggerTemplate of name 'foo' in namespace 'bar':
tkn triggertemplate describe foo -n bar
or, if you're feeling efficient and love a shortcut:
tkn tt desc foo -n bar
both slay. same energy. π¦
π SEE ALSO π
tkn-triggertemplate(1)β go read the parent, bestie, it's where all of this comes from π«Ά
lowkey a reminder that this whole page was auto generated by spf13/cobra β so nobody hand-wrote this, it just manifested β¨
okay that's the page!! and for the sign-off β this gem is Auto generated by spf13/cobra, from the TKN-TRIGGERTEMPLATE-DESCRIBE(1) manual, and it's dated TKN-TRIGGERTEMPLATE-DESCRIBE(1) era (the footer literally just repeats the title, which is such a mood honestly π). love u, go describe some TriggerTemplates ππ
π¦ where this page comes from
- nixos 26.05: tektoncd-cli 0.45.0
- nixpkgs unstable: tektoncd-cli 0.46.2
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms