Overview:

Users want a form based edit experience for Config Maps. This was something that was provided in 3.x, but is lacking in 4.x.

Goal:

Provide a form based creation and edit experience for Config Maps.

Why is it important?

Many developers don't want to deal with YAML.
We want to simplify the e2e experience for developers working with OpenShift.

Use cases:

1. <case>

Acceptance criteria:

1. When creating a Config Map, users should be provided a form driven experience
2. When editing a Config Map, users should be provided a form driven experience
3. Users should be able to switch from form to YAML mode when creating or editing a config map

Dependencies (External/Internal):

None

Design Artifacts:

Reference 3.x form & existing standards

Exploration:

Note: