Oc edit: Difference between revisions
Jump to navigation
Jump to search
| Line 15: | Line 15: | ||
oc edit supports the following generic syntax: | oc edit supports the following generic syntax: | ||
oc edit ''<[[ | oc edit ''<[[OpenShift_Concepts#Objects|componentType]]>''/''<componentName>'' [-o json] | ||
The default format is YAML. | The default format is YAML. | ||
| Line 26: | Line 26: | ||
The same pattern applies for [[oc describe#Generic_Syntax|oc describe]]. | The same pattern applies for [[oc describe#Generic_Syntax|oc describe]]. | ||
For a complete list of OpenShift component types, see {{Internal| | For a complete list of OpenShift component types, see {{Internal|OpenShift_Concepts#Objects|OpenShift Objects}} | ||
=Sub-Commands= | =Sub-Commands= | ||
oc edit project ''<project-name>'' | oc edit project ''<project-name>'' | ||
Latest revision as of 20:26, 31 January 2018
Internal
Overview
In-line metadata editing with vi. Exposes the metadata in YAML or JSON format for editing.
Changes are persisted immediately, and then OpenShift attempts to run oc update using the configuration file.
If an error occurs during the update process, the configuration is reverted to the original state. The modified configuration is saved in a temporary folder. The folder can be accessed and the update can be run again.
Generic Syntax
oc edit supports the following generic syntax:
oc edit <componentType>/<componentName> [-o json]
The default format is YAML.
oc edit daemonset/logging-fluentd oc edit node/node1 oc edit pod/logging-fluentd-3kz30 oc edit oauthclient/kibana-proxy
The same pattern applies for oc describe.
For a complete list of OpenShift component types, see
Sub-Commands
oc edit project <project-name>