Oc edit: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 7: Line 7:
In-line metadata editing with vi. Exposes the metadata in YAML or JSON format for editing.
In-line metadata editing with vi. Exposes the metadata in YAML or JSON format for editing.


After saving the changes, OpenShift attempts to run [[Oc update#Overview|oc update]] using the configuration file.  
Changes are persisted immediately, and then OpenShift attempts to run [[Oc update#Overview|oc update]] using the configuration file.  


{{Warn|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.}}
{{Warn|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.}}

Revision as of 18:05, 21 November 2017

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

OpenShift Component Types

Sub-Commands

oc edit project <project-name>