TKN-TRIGGERTEMPLATE-DESCRIBE(1)

πŸ“¦ version 0.46.2, in nixos 26.05, nixpkgs unstable

πŸ’… 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 for describe. 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 the managedFields when printing objects in JSON or YAML format. 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-template or -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 your KUBECONFIG for 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 πŸ’€


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