Repository navigation
Resurrection #87
Description
Now that several external platform components have stabilized, it's time to move over to them and move forward:
- Move to .NET Core/Standard 2.x:
-
TugDSC.Abstractions(formerlyTug.Base)- Tests
-
TugDSC.Server.Abstractions(formerlyTug.Server.Base) -
TugDSC.Server.WebAppHost(formerlyTug.Server)- Tests
-
TugDSC.Client.CLIApp(formerlyTug.Client)- Tests
-
TugDSC.Server.FaaS.AwsLambda(formerlyTug.Server.FaaS.AwsLambda)
-
- Move to PowerShell Core v6
-
TugDSC.Server.Providers.PS6Handler(replacesTug.Server.Providers.Ps5DscHandler)
-
- Rework the extension loading mechanism -- it's unnecessarily, overly complex -- move away from MEF for now.
- Clean up the "bundling" process and release bundles for more configurations
- Start work on Admin API endpoint and supporting client cmdlets
- Come up with a good solution for encrypted config elements (e.g. passwords)
- Start work on UI layer
Activity
First major commit in support of #87
zfilipov commentedon Apr 18, 2018
All,
We are currently leveraging this product for our project. We appreciate all of your time and effort that has gone into this, it is a great pull server solution for PowerShell DSC. We are looking to update our codebase for Tug, so I was checking in to see if there is a release for .NET Core 2.0 on the horizon.
ebekker commentedon Apr 25, 2018
It's coming -- slowly but surely.