TKN-PIPELINERUN-EXPORT(1)

💅 TKN-PIPELINERUN-EXPORT — bestie's guide to yeeting a PipelineRun out as yaml

okay so real talk: this is page TKN-PIPELINERUN-EXPORT(1) of the manual, and it's all about the export subcommand. you already know the family name (tkn), this is the one that grabs a PipelineRun and hands it to you in a format you can copy around. let's get into it 🫶

---

✨ NAME ✨

tkn-pipelinerun-export — Export PipelineRun

like, literally the whole job. export a PipelineRun. that's it, that's the girl 💅

---

🦋 SYNOPSIS 🦋

tkn pipelinerun export

short and sweet, no cap ✨

---

🌸 DESCRIPTION 🌸

Export PipelineRun

yes bestie that's genuinely the entire description, the original manpage is a woman of few words and i respect it 😭

---

🎀 OPTIONS 🎀

here's where it gets juicy. every flag, none skipped, i would never 🙈

• --allow-missing-template-keys[=true] — if true, it just ignores any errors in templates when a field or map key is missing in the template. like, no drama, we move. ⚠️ heads up: this only applies to golang and jsonpath output formats — don't come for it in other formats, it's not invited there.
• -h, --help[=false] — help for export. the classic "what does this even do" button, iconic as always 👑
• -o, --output="" — the output format, queen of the whole command 💖 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, keep the managedFields when printing objects in JSON or YAML format. lowkey niche but slay if you need it ✨
• --template="" — a template string, or path to a template file, to use when -o=go-template or -o=go-template-file. the template format is golang templates [ http://golang.org/pkg/text/template/#pkg-overview ]. go off with your custom formatting 🧚

---

🧚 OPTIONS INHERITED FROM PARENT COMMANDS 🧚

these come from the parent command, so you get them for free, no cap 🫶

• -c, --context="" — name of the kubeconfig context to use (default: kubectl config current-context). choose your universe 🌈
• -k, --kubeconfig="" — kubectl config file (default: $HOME/.kube/config). your config, your rules 💜
• -n, --namespace="" — namespace to use (default: from $KUBECONFIG). home base bestie 🏠
• -C, --no-color[=false] — disable coloring (default: false). for when the rainbow is Too Much (rare, but valid) 💀

---

🔥 EXAMPLE 🔥

Export PipelineRun Definition:

tkn pipelinerun export will export a pipelinerun definition as yaml to be easily
imported or modified.

Example: export a PipelineRun named 'pipelinerun' in namespace 'foo' and recreate
it in the namespace 'bar':

tkn pr export pipelinerun -n foo|kubectl create -f- -n bar

see what's happening? you pull the definition out of namespace foo, pipe it straight into kubectl create pointed at namespace bar, and boom — copy-paste relocation of a whole PipelineRun. it's giving main character energy fr fr ⭐

---

🌟 SEE ALSO 🌟

• tkn-pipelinerun(1) — go hang out with the parent page, she has more where this came from 💖

---

aaaand that's the whole page bestie 🎀 this beauty is Auto generated by spf13/cobra, and it's <rainbow>TKN-PIPELINERUN-EXPORT(1)</rainbow> — same name top and bottom, symmetric queen 💅 go forth and export responsibly ✨