Uploaded image for project: 'Modules'
  1. Modules
  2. MODULES-7590

IIS : Setting 'No Managed Code' results in intentional change "Loop"

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Minor
    • Resolution: Duplicate
    • None
    • None
    • iis
    • Windows Server 2016 Desktop Experience

    • MODULES Bug Template
    • Windows
    • Needs Assessment
    • Reviewed
    • Needs Assessment

    Description

      When setting an application pool to run as 'No Managed Code', the Puppet Forge documentation (v. 4.3.2) suggests setting managed_runtime_version => '""',. This should result in the application pool running as 'No Managed Code'

       

      While this seems to function as intended, the node will continually loop through an intentional change:

       

      2018-08-06
      14:53 Z
      notice managed_runtime_version changed '' to '""' * Source:/Stage[main]/REDACTED_web_services::REDACTED/Iis_application_pool[REDACTED]/managed_runtime_version
      • File:/opt/fidPuppet/code/environments/dev/modules/custom_modules/REDACTED_web_services/manifests/REDACTED.pp
      • Line:114

      Example Code causing this behavior:

        # Sets managed runtime version to no managed code
        iis_application_pool { 'REDACTED':
          ensure                  => 'present',
          managed_pipeline_mode   => 'Integrated',
          managed_runtime_version => '""',
          state                   => 'Started',
          auto_start              => true,
          identity_type           => 'SpecificUser',
          user_name               => $iis_user,
          password                => $iis_password,
        }
       
      
      

       

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              michaelgg13 Michael Gerhart
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support