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

Replace FACTER_url with --resource for puppet device

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 5.3.6, PUP 5.5.0
    • Component/s: None
    • Labels:
    • Template:
    • Team:
      Modules
    • Release Notes:
      New Feature
    • Release Notes Summary:
      Adds the ability to retrieve current system state as Puppet code from devices using `puppet device`.
    • QA Risk Assessment:
      Needs Assessment

      Description

      Since 2012, we've used FACTER_url as a workaround for puppet resource:

      A limitation to watch out for in the current Puppet release is that 'puppet apply' and 'puppet resource' cannot modify network resources. However, we implemented a feature to allow puppet resource to query a F5 device. (For authors of types/providers, making changes to resources aren’t supported until apply_to_device in resources type are handled differently by puppet apply/resource commands). For now we use url facts to establish connectivity to specific F5 devices.

      https://puppet.com/blog/managing-f5-big-ip-network-devices-puppet

      Using FACTER_url is insecure, as it places authentication credentials either in history or in the environment. It's also ugly.

      If we implement --target in puppet resource as we've done in puppet device we can lookup the target device's url and internally set {{Facter(:url). This would not require changes to existing device modules.

      If we implement this as a device(name) method in Puppet::Util::NetworkDevice::Config, it would allow device tasks to use device(name) to target devices.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              richard.sherman Rick Sherman
              Reporter:
              tom.kishel Thomas Kishel
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support