Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: puppetlabs/ruby-pwsh
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 0.7.3
Choose a base ref
...
head repository: puppetlabs/ruby-pwsh
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 0.7.4
Choose a head ref
  • 7 commits
  • 4 files changed
  • 4 contributors

Commits on Feb 3, 2021

  1. Merge pull request #103 from puppetlabs/release

    (MAINT) Mergeback 0.7.3 Release
    sanfrancrisko authored Feb 3, 2021
    Configuration menu
    Copy the full SHA
    f064862 View commit details
    Browse the repository at this point in the history

Commits on Feb 11, 2021

  1. (GH-105) Ensure canonicalized_cache check validates against namevar

    Prior to this commit the safety check in the canonicalize method intended to prevent
    multiple executions to canonicalize the same resource compared the cached resources
    to the *full* resource being checked; this commit changes that check to only search
    for a hash containing the matching namevars.
    
    This should prevent multiple runs and bugs where mandatory parameters are dropped
    during an RSAPI refresh event.
    michaeltlombardi committed Feb 11, 2021
    Configuration menu
    Copy the full SHA
    1d1d0b3 View commit details
    Browse the repository at this point in the history
  2. Merge pull request #107 from michaeltlombardi/gh-105/main/check-canon…

    …ical-cache-on-namevar
    
    (GH-105) Ensure canonicalized_cache check validates against namevar
    RandomNoun7 authored Feb 11, 2021
    Configuration menu
    Copy the full SHA
    89cef9b View commit details
    Browse the repository at this point in the history
  3. (GH-105) Ensure set runs on ambiguous ensure states

    Prior to this commit if a resource is ensurable but the value of ensure on
    the target node was not Present or Absent the call to run Invoke-DscResource
    never gets made.
    
    This commit updates the logic in the set method to call update() if the state
    of the ensurable resource is ambiguous from a CRUD perspective, which is
    preferable to not running set at all.
    michaeltlombardi committed Feb 11, 2021
    Configuration menu
    Copy the full SHA
    ea1a013 View commit details
    Browse the repository at this point in the history

Commits on Feb 12, 2021

  1. Merge pull request #108 from michaeltlombardi/gh-105/main/call-update…

    …-on-ambiguous-ensure
    
    (GH-105) Ensure set runs on ambiguous ensure states
    michaeltlombardi authored Feb 12, 2021
    Configuration menu
    Copy the full SHA
    65b23a6 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    5cca17c View commit details
    Browse the repository at this point in the history
  3. Merge pull request #109 from michaeltlombardi/maint/release/prep-074

    (MAINT) Prep for 0.7.4 release
    michaeltlombardi authored Feb 12, 2021
    Configuration menu
    Copy the full SHA
    23b8a26 View commit details
    Browse the repository at this point in the history
Loading