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

xFailOverCluster: Update manifest and license with the new year 2018 #167

Closed
johlju opened this issue Jan 1, 2018 · 0 comments · Fixed by #168
Closed

xFailOverCluster: Update manifest and license with the new year 2018 #167

johlju opened this issue Jan 1, 2018 · 0 comments · Fixed by #168
Assignees
Labels
enhancement The issue is an enhancement request.

Comments

@johlju
Copy link
Member

johlju commented Jan 1, 2018

Details of the scenario you tried and the problem that is occurring:
We should update the manifest and license with 2018 after the new year.

The DSC configuration that is using the resource (as detailed as possible):
n/a

Version of the Operating System and PowerShell the DSC Target Node is running:
n/a

Version of the DSC module you're using, or 'dev' if you're using current dev branch:
Dev

@johlju johlju added enhancement The issue is an enhancement request. in progress The issue is being actively worked on by someone. labels Jan 1, 2018
johlju added a commit to johlju/FailoverClusterDsc that referenced this issue Jan 1, 2018
- Updated year to 2018 in license file and module manifest (issue dsccommunity#167).
johlju added a commit that referenced this issue Jan 1, 2018
- Changes to xFailoverCluster
  - Updated year to 2018 in license file and module manifest (issue #167).
@johlju johlju removed the in progress The issue is being actively worked on by someone. label Jun 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement The issue is an enhancement request.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant