Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

xDnsServerADZone: Removed CimSession from Get-TargetResource return value (Fixes #40) #49

Merged
merged 3 commits into from
Aug 9, 2017

Conversation

BernieWhite
Copy link
Contributor

@BernieWhite BernieWhite commented May 22, 2017

Fix for #40

Added fix, updated unreleased changes and added unit test.

When checking other resources such as xDnsServerPrimaryZone and xDnsServerSecondaryZone they also did not return a CimSession key. I have removed CimSession from the return of Get-TargetResource within xDnsServerADZone for consistency.


This change is Reviewable

@msftclas
Copy link

@BernieWhite,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

@BernieWhite BernieWhite changed the title Bewhite/patch 1 Removed CimSession from xDnsServerADZone Get-TargetResource May 22, 2017
@BernieWhite
Copy link
Contributor Author

Existing readme.md fails tests. Fixed tabs with space indents.

@BernieWhite BernieWhite changed the title Removed CimSession from xDnsServerADZone Get-TargetResource xDnsServerADZone: Removed CimSession from Get-TargetResource return value (Fixes #40) May 30, 2017
@BernieWhite
Copy link
Contributor Author

@kwirkykat Any thoughts Katie?

@kwirkykat kwirkykat merged commit b44e201 into dsccommunity:dev Aug 9, 2017
johlju pushed a commit that referenced this pull request Apr 20, 2018
- Fixed all PSSA rule warnings.
- Changes to xDnsServerADZone
  -  Fixed bug introduced by issue #49. Previously, CimSessions were always used
     regardless of connecting to a remote machine or the local machine. Now
     CimSessions are only utilized when a ComputerName, or ComputerName and
     Credential are used (issue #53).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants