OC-APPLY-EDIT-LAST-APPLIED(1)

✨ NAME ✨

okay so bestie, welcome to the OC APPLY(1) manual page — this command is oc apply edit-last-applied, and its whole job is: Edit latest last-applied-configuration annotations of a resource/object. 💅

🌸 SYNOPSIS 🌸

oc apply edit-last-applied [OPTIONS]

🦋 DESCRIPTION 🦋

okay so edit-last-applied is literally the glow-up editor for the latest last-applied-configuration annotations of resources, and it opens them in your default editor. ✨

The edit-last-applied command lets you directly edit any API resource you can retrieve via the command-line tools. It opens the editor defined by your KUBE_EDITOR or EDITOR environment variables, or falls back to vi for Linux or notepad for Windows. You can edit multiple objects, but no cap: changes are applied one at a time. The command accepts file names as well as command-line arguments, although the files you point to must be previously saved versions of resources. 🫶

The default format is YAML. To edit in JSON, specify -o json. 🎀

The flag --windows-line-endings can be used to force Windows line endings, otherwise the default for your operating system will be used. 🌈

🚨 in the event an error occurs while updating, a temporary file will be created on disk that contains your unapplied changes. The most common error when updating a resource is another editor changing the resource on the server. When this occurs, you will have to apply your changes to the newer version of the resource, or update your temporary saved copy to include the latest resource version. no cap, do not ignore this bestie 😭

👑 OPTIONS 👑

these are the flags, one bullet each, no skipping fr fr:

• --allow-missing-template-keys=true — if true, ignore any errors in templates when a field or map key is missing in the template. Only applies to golang and jsonpath output formats. 💖
• --field-manager="kubectl-client-side-apply" — name of the manager used to track field ownership. 👑
• -f, --filename=[] — filename, directory, or URL to files to use to edit the resource. 🎀
• -k, --kustomize="" — process the kustomization directory. This flag can't be used together with -f or -R. ⚠️
• -o, --output="" — output format. One of: (json, yaml, kyaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). ✨
• -R, --recursive=false — process the directory used in -f, --filename recursively. Useful when you want to manage related manifests organized within the same directory. 🌀
• --show-managed-fields=false — if true, keep the managedFields when printing objects in JSON or YAML format. 🫶
• --template="" — template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates (⟨http://golang.org/pkg/text/template/#pkg-overview⟩). 🌸
• --validate="ignore" — must be one of: strict (or true), warn, ignore (or false). "true" or "strict" will use a schema to validate the input and fail the request if invalid. It will perform server side validation if ServerSideFieldValidation is enabled on the api-server, but will fall back to less reliable client-side validation if not. "warn" will warn about unknown or duplicate fields without blocking the request if server-side field validation is enabled on the API server, and behave as "ignore" otherwise. "false" or "ignore" will not perform any schema validation, silently dropping any unknown or duplicate fields. 💀
• --windows-line-endings=false — defaults to the line ending native to your platform. 🪟

💜 OPTIONS INHERITED FROM PARENT COMMANDS 💜

these came from the parent command like hand-me-downs but make it kubeconfig:

• --as="" — username to impersonate for the operation. User could be a regular user or a service account in a namespace. 🫶
• --as-group=[] — group to impersonate for the operation, this flag can be repeated to specify multiple groups. 👯
• --as-uid="" — UID to impersonate for the operation. 🆔
• --as-user-extra=[] — user extras to impersonate for the operation, this flag can be repeated to specify multiple values for the same key. 🔑
• --cache-dir="/homeless-shelter/.kube/cache" — default cache directory. 🗂️
• --certificate-authority="" — path to a cert file for the certificate authority. 📜
• --client-certificate="" — path to a client certificate file for TLS. 🔐
• --client-key="" — path to a client key file for TLS. 🔑
• --cluster="" — the name of the kubeconfig cluster to use. ☸️
• --context="" — the name of the kubeconfig context to use. 🧭
• --disable-compression=false — if true, opt-out of response compression for all requests to the server. 📦
• --insecure-skip-tls-verify=false — if true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure. 🚨
• --kubeconfig="" — path to the kubeconfig file to use for CLI requests. 📁
• --kuberc="" — path to the kuberc file to use for preferences. This can be disabled by exporting KUBECTL_KUBERC=false feature gate or turning off the feature KUBERC=off. 🛠️
• --match-server-version=false — require server version to match client version. 🧩
• -n, --namespace="" — if present, the namespace scope for this CLI request. 🏷️
• --profile="none" — name of profile to capture. One of (none|cpu|heap|goroutine|threadcreate|block|mutex). 📈
• --profile-output="profile.pprof" — name of the file to write the profile to. 📝
• --request-timeout="0" — the length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests. ⏳
• -s, --server="" — the address and port of the Kubernetes API server. 🌐
• --tls-server-name="" — server name to use for server certificate validation. If it is not provided, the hostname used to contact the server is used. 🛡️
• --token="" — bearer token for authentication to the API server. 🎟️
• --user="" — the name of the kubeconfig user to use. 👤
• --warnings-as-errors=false — treat warnings received from the server as errors and exit with a non-zero exit code. ⚠️

🌈 EXAMPLE 🌈

okay examples, because seeing it is believing:

# Edit the last-applied-configuration annotations by type/name in YAML
oc apply edit-last-applied deployment/nginx

# Edit the last-applied-configuration annotations by file in JSON
oc apply edit-last-applied -f deploy.yaml -o json

🎀 SEE ALSO 🎀

the one and only see-also bestie: oc-apply(1), 💖

⭐ HISTORY ⭐

June 2016 — Ported from the Kubernetes man-doc generator. iconic origin story, honestly. 💅

🌸 that's the whole page, bestie — brought to you by Openshift / Openshift CLI User Manuals, page OC APPLY(1), dated June 2016. periodt, stay slaying 💖