Skip to content

Fix issue where EndDate parameter was not being honored for AD cmdlets #7710

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

Merged
merged 3 commits into from
Nov 1, 2018

Conversation

cormacpayne
Copy link
Member

@cormacpayne cormacpayne commented Oct 31, 2018

Description

Fix for #7700

There are a few cmdlets that don't respect the value of -EndDate parameter, or don't get the accurate "one year after start date" default value, which is fixed in this PR.

Checklist

@markcowl markcowl changed the base branch from preview to release-2018-11-06 October 31, 2018 18:00
}

public override void ExecuteCmdlet()
{
if (!this.IsParameterBound(c => c.EndDate))
Copy link
Member

Choose a reason for hiding this comment

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

A mocked test to prevent regressing this would be nice

@markcowl markcowl merged commit 9a27595 into Azure:release-2018-11-06 Nov 1, 2018
@cormacpayne cormacpayne deleted the new-sp-cred-fix branch January 16, 2019 21:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants