Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-4755

Puppet config set --section main foo bar does not set or respect an empty [main] section

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 5.4.0
    • Component/s: None
    • Labels:
    • Template:
    • Team:
      Platform Core
    • Story Points:
      2
    • Sprint:
      Platform Core KANBAN
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      When specifying {{--section main}} with the {{puppet config set}} command, an explicit [main] section header is now added to the config file.
    • QA Risk Assessment:
      No Action
    • QA Risk Assessment Reason:
      tests cover testing

      Description

      With a puppet.conf that does not have a [main] section, `puppet config set --section main foo bar` does not create a [main] section.

      With a puppet.conf that has an empty [main] section, `puppet config set --section main foo bar` places the setting at the top of the file, outside of the [main] section.

      Both cases I believe are because it the default section is treated as '[main]'

      This only came up because we test for augeas functionality on puppet.conf in PE, and augeas does not like to parse a puppet.conf with settings that are not in a section, and the pe_repo adds settings to [main], but the default puppet.conf no longer has sections...

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              joshua.partlow Joshua Partlow
              QA Contact:
              Eric Delaney Eric Delaney
              Votes:
              3 Vote for this issue
              Watchers:
              11 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support