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

Running puppet with no arguments should allow a default operation to specified in puppet.conf

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Normal
    • Resolution: Won't Do
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Template:

      Description

      One of the more interesting thing I have noticed and liked about other industry tools like chef-client, is that it is a single command. I think puppet is often more complicated then it needs to be for common operations. I think it would be nice to be able to specify somthing like `default_args` in puppet.conf to allow novice users to simply run `puppet` and have default args set to `'agent -t'`. Right now running puppet with no arguments holds no value, and because we have confusing arguments, new users have to learn concepts like `--test` is 3 arguments put together, they also often confuse apply and agent when first learning puppet. If am the administator of puppet , it would be nice to have a pre-canned set of arguments that I could specify from the command line, especially for things like `--environment foo` where I could manage that and just teach developers `puppet`. I think this would lower the price of admission for such a common command.

      We could default it to show the current behavior "See 'puppet help' for help on available puppet subcommands" if the puppet.conf entry is not there, and we could have a notice at the beginning of the runs saying something like "using default_args: puppet agent -t --noop --environment foo" to take some of the magic out of it.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              zack.smith Zack Smith
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Zendesk Support