Skip to main content

Console resource editor

Available

Deployed and supported. The fields and commands described here are stable within version v1alpha1.

The console offers a single editor to create and edit your resources: Registry, Monitoring, Applications, or any kind from Create a resource. It replaces the raw YAML display: the Edit button opens the editor.

Two synchronized tabs​

  • Form: the resource fields, generated from its manifest. Objects and lists are collapsible blocks; values keep their type (number, checkbox for a boolean, text: "8080" stays text). You can rename or delete a field, add one (the value {} or [] is accepted) and add a list item, which takes the shape of the last one.
  • YAML: the full manifest, with syntax highlighting, line numbers and a Copy button.

A change in one tab shows up right away in the other. Fields the editor does not know are kept as they are, and so are the comments in your YAML.

If the YAML is invalid, the YAML tab shows an error indicator, the faulty line is highlighted with its message, and the form keeps the last valid state until you fix it.

Create a resource​

  1. Choose Create a resource, then the kind you want.
  2. Start from a catalog template (see Manifest templates) or from a minimal skeleton of the kind: apiVersion, kind and metadata.name. Your tenant is always the one you are signed in with; you never enter it.
  3. Fill in the form or the YAML, then Save.

Several objects at once​

When creating, separate objects with --- in the YAML tab: each becomes a block of the form. The whole set is validated before the first one is saved; if a single object is refused, none is created. To edit an existing resource, the YAML contains a single object.

Understand a refusal​

Before saving, the console checks the manifest like sng validate. Each refusal is shown on the field concerned in the form and on the matching YAML line, with the reason. Fix it, then save again.

Fields the platform fills in itself (such as status) are read-only or hidden.

On a phone​

The editor works one-handed: the page does not scroll sideways (only the YAML does), key/value fields stack, buttons are large enough for a finger, autocorrect is off in YAML fields, and Save / Cancel stay pinned at the bottom of the screen.

See also​