Resurrection

[ebekker]

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 (formerly Tug.Base)
    • Tests
  • TugDSC.Server.Abstractions (formerly Tug.Server.Base)
  • TugDSC.Server.WebAppHost (formerly Tug.Server)
    • Tests
  • TugDSC.Client.CLIApp (formerly Tug.Client)
    • Tests
  • TugDSC.Server.FaaS.AwsLambda (formerly Tug.Server.FaaS.AwsLambda)
• Move to PowerShell Core v6
  • TugDSC.Server.Providers.PS6Handler (replaces Tug.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

[zfilipov]

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]

It's coming -- slowly but surely.