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

Puppet should have a way of defining properties or parameters for types as sensitive

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Normal
    • Resolution: Fixed
    • None
    • PUP 6.0.0
    • None
    • None
    • Platform Core
    • Platform Core KANBAN
    • Needs Assessment
    • New Feature
    • Parameters can now be marked sensitive at the class level rather then just the instance level.
    • Manual

    Description

      Currently we have this lovely dance we need to go through if we need to define a parameter or property as sensitive. You can see examples of this in file.rb and exec.rb (https://github.com/puppetlabs/puppet/commit/abd866a648a32d3895011d25af5d4b3d994669c8) As it currently works, we can only set a specific instance as sensitive. We should be able to say all instances of a particular property/parameter are sensitive when defining it.

       

      Attachments

        Issue Links

          relates to

          New Feature - A new feature of the product, which has yet to be developed. PUP-7400 yumrepo provider should support username and password

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. PUP-9249 Backport sensitive DSL method PUP-8514

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Resolved

          New Feature - A new feature of the product, which has yet to be developed. PUP-10961 Add option to declare parameters and properties as sensitive without the set_sensitive_parmeters

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Accepted

          Activity

            People

              jorie Jorie Tappa
              melissa Melissa Stone
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support