Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-61393

Import YAML editor has tab default to 4 spaces

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Undefined Undefined
    • 4.21.0
    • 4.20
    • Management Console
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Moderate
    • None
    • None
    • None
    • None
    • Done
    • Bug Fix
    • Hide
      Before this update, the YAML editor in the web console would default to indenting YAML files with four spaces. With this release, the default indentation has changed to two spaces to align with recommendations. (link:https://issues.redhat.com/browse/OCPBUGS-61393[OCPBUGS-61393])
      Show
      Before this update, the YAML editor in the web console would default to indenting YAML files with four spaces. With this release, the default indentation has changed to two spaces to align with recommendations. (link: https://issues.redhat.com/browse/OCPBUGS-61393 [ OCPBUGS-61393 ])
    • None
    • None
    • None
    • None

      Description of problem:

      Import YAML editor use 4 spaces for indentation     

      Version-Release number of selected component (if applicable):

      4.20.0-0.nightly-2025-09-08-182033    

      How reproducible:

      Always    

      Steps to Reproduce:

      1. Click on +(plus) icon in masthead -> Import YAML 
      2. in the YAML editor, type following YAML snippet, press Enter after typing "metadata:"
      
      
      kind: ConfigMap
      apiVersion: v1
      metadata: 
         

      Actual results:

      3. we can see 4 spaces for indentation 

      Expected results:

      3. It looks like more suggested syntax for YAML files is to use 2 spaces for indentation

      Additional info:

          

              rh-ee-jaclee Jackson Lee
              rhn-support-yapei YaDan Pei
              None
              None
              YaDan Pei YaDan Pei
              None
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: