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

Seems like all xDscResources are shipping with .git and .vscode #470

Closed
csharmath opened this Issue Dec 4, 2018 · 6 comments

Comments

Projects
None yet
3 participants
@csharmath
Copy link

csharmath commented Dec 4, 2018

I've noticed this with xWebAdministration first
PowerShell/xWebAdministration#406

Then saw it with xExchange
PowerShell/xExchange#342

Then checked a couple of the xDSC resources and all of them are shipping with .git and .vscode, etc.
So something is missed on the deployment pipeline and I thought that it's more appropriate to file the issue here.

@PlagueHO

This comment has been minimized.

Copy link
Contributor

PlagueHO commented Dec 5, 2018

@kwirkykat - this does seem to be the case with some of the resources that went out in the most recent resource kit release.

The following resources have been affected:

  • AuditPolicyDsc
  • DFSDsc
  • SecurityPolicyDsc
  • xBitlocker
  • xExchange
  • xHyper-V

The following resources that were released in Nov are not affected:

  • NetworkingDsc
  • SharePointDsc
  • StorageDsc

xWebAdministration is affected but did not get deployed in the Nov DSC resource kit release. So this might have been occurring for a while.

@PlagueHO

This comment has been minimized.

Copy link
Contributor

PlagueHO commented Dec 22, 2018

@mgreenegit , @kwirkykat - any update on this one?

@johlju

This comment has been minimized.

Copy link
Contributor

johlju commented Jan 3, 2019

I agree that @kwirkykat should look into this one before the next release. 🙂

Updating to prevent the issue from being stale.

@PlagueHO

This comment has been minimized.

Copy link
Contributor

PlagueHO commented Jan 10, 2019

Just so we have a link to the root cause:
PowerShell/PowerShellGet#378

@PlagueHO

This comment has been minimized.

Copy link
Contributor

PlagueHO commented Jan 10, 2019

It does look like the recent release that went out has not included the problem files. Should we close this one?

@csharmath

This comment has been minimized.

Copy link

csharmath commented Jan 10, 2019

This is getting resolved with PowerShell/PowerShellGet#395

@csharmath csharmath closed this Jan 10, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment