Skip to content
This repository has been archived by the owner on Jun 14, 2024. It is now read-only.

Added support for Exclusive flag parameter which ensures the a value is the EXCLUSIVE value in a given key. #64

Open
wants to merge 2 commits into
base: dev
Choose a base branch
from

Conversation

bobbytreed
Copy link

@bobbytreed bobbytreed commented May 30, 2017

Other resources (like UserRightsAssignment) perform this operation with the FORCE parameter. Here the FORCE parameter is used to remove Keys that have subkeys. Other names can be considered, but a flag is the most logical option. The impact is low for this change as current implementations would not at all be affected.

Fixes #63


This change is Reviewable

@codecov-io
Copy link

codecov-io commented May 30, 2017

Codecov Report

Merging #64 into dev will decrease coverage by <1%.
The diff coverage is 65%.

Impacted file tree graph

@@         Coverage Diff         @@
##            dev    #64   +/-   ##
===================================
- Coverage    83%    83%   -1%     
===================================
  Files        19     19           
  Lines      2751   2780   +29     
  Branches      4      5    +1     
===================================
+ Hits       2294   2313   +19     
- Misses      453    462    +9     
- Partials      4      5    +1

@@ -332,6 +363,20 @@ function Set-TargetResource
$null = Remove-Item -Path $Key -Recurse -Force
}
}
else
{
if ($Exclusive)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add a comment about why are removing:

  • key exist
  • value name not specified
  • Exclusive specified

So remove any values.

@zjalexander
Copy link

Discussing some design patterns with Bobby offline.

@kwirkykat kwirkykat added the on hold The issue or pull request has been put on hold by a maintainer. label Jun 27, 2017
@PowerShell PowerShell deleted a comment from msftclas Sep 27, 2017
@mbreakey3
Copy link
Member

Are there any updates on this PR or has it been abandoned for the time being?

@zjalexander
Copy link

We were discussing design implications with Mark. Since Mark has moved on, let me loop @mgreenegit in.

@johlju
Copy link
Contributor

johlju commented Apr 30, 2018

@mgreenegit Can you glance at this PR so we can remove the 'on hold' label, and then we can review it.

@bobbytreed Are you still able to work on this issue if we can remove the 'on hold' label?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
on hold The issue or pull request has been put on hold by a maintainer.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants