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

πŸ“¦
version 4.22.0 Β· 2 versions
, in nixpkgs unstable

πŸ’… OC APPLY(1) β€” your oc apply set-last-applied era β€” from the Openshift CLI User Manuals fam, June 2016 edition ✨

πŸ’– NAME πŸ’–

oc apply set-last-applied β€” set the last-applied-configuration annotation on a live object so it matches the contents of a file. that's the whole assignment, bestie πŸ‘‘

πŸ¦‹ SYNOPSIS πŸ¦‹

oc apply set-last-applied [OPTIONS]

🌸 DESCRIPTION 🌸

okay so this command sets the latest last-applied-configuration annotations by setting it to match the contents of a file. this results in the last-applied-configuration being updated as though oc apply -f<file> was run, without updating any other parts of the object. it's giving surgical annotation glow-up, not a whole-object rewrite πŸ’…

πŸŽ€ OPTIONS πŸŽ€

  • --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 ✨
  • --create-annotation=false β€” will create 'last-applied-configuration' annotations if current objects doesn't have one. (the grammar is canon, don't come for me 😭)
  • --dry-run="none" β€” must be "none", "server", or "client". if client strategy, only print the object that would be sent, without sending it. if server strategy, submit server-side request without persisting the resource.
  • -f, --filename=[] β€” filename, directory, or URL to files that contains the last-applied-configuration annotations.
  • -o, --output="" β€” output format. one of: (json, yaml, kyaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file).
  • --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].

🌈 OPTIONS INHERITED FROM PARENT COMMANDS 🌈

  • --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 these are the exact examples, copy-paste energy:

                # Set the last-applied-configuration of a resource to match the contents of a file
                oc apply set-last-applied -f deploy.yaml

                # Execute set-last-applied against each configuration file in a directory
                oc apply set-last-applied -f path/

                # Set the last-applied-configuration of a resource to match the contents of a file; will create the annotation if it does not already exist
                oc apply set-last-applied -f deploy.yaml --create-annotation=true

πŸ”— SEE ALSO πŸ”—

πŸ“œ HISTORY πŸ“œ

June 2016, Ported from the Kubernetes man-doc generator.


that's the whole page, bestie 🫢 β€” brought to you by Openshift and the Openshift CLI User Manuals, dated June 2016. now go set those last-applied annotations and absolutely slay βœ¨πŸ‘‘πŸ’…

πŸ“¦ where this page comes from