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

IIS: Trying to set 'No Managed Code' not working

    Details

    • Template:
      MODULES Bug Template
    • Acceptance Criteria:
      Hide

       Able to set an IIS Application Pool to have no managed code idempotently without error.
       New acceptance tests to verify this functionality exist and pass in CI
       Reference documentation for the managed_runtime_version explains how to specify no managed code.
       Narrative documentation in the Usage section for specifying no managed code is updated.

      Show
       Able to set an IIS Application Pool to have no managed code idempotently without error.  New acceptance tests to verify this functionality exist and pass in CI  Reference documentation for the managed_runtime_version explains how to specify no managed code.  Narrative documentation in the Usage section for specifying no managed code is updated.
    • Team:
      Windows
    • CS Priority:
      Reviewed
    • QA Risk Assessment:
      Needs Assessment

      Description

      PE Version: 2018.1.2

      OS: Windows server 2016

      This has arisen from another Jira where a customer was setting 'no managed code' in an older version of the module and this was causing unintentional changes on each puppet run.

      When I tried to replicate this behaviour, I couldn't but ran into a new issue when trying to set this.

      Once I set managed_runtime_version => '""' it set .NET CLR version in ISS to "" rather than "No managed code" as seen in the attached screenshot:

      This should set .NET CLR version to "no managed code" as described in our complete code example here: https://forge.puppet.com/puppetlabs/iis#usage

      The customer has just recently updated to the latest version (4.4.0) of the module and has now run into this issue as well.

      The code the customer and I have used is as follows:

        # 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,
        }
      

       

      Here is the previous Jira that this issue has arisen from for reference: https://tickets.puppetlabs.com/browse/MODULES-7590

       

        Attachments

          Issue Links

            Activity

              jsd-sla-details-panel

                People

                • Assignee:
                  michael.lombardi Michael Lombardi
                  Reporter:
                  patrick.grant Patrick Grant
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  6 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: