Azure uses YAML. Please finally add ConvertFrom-Yaml, ConvertTo-Yaml #16785

Activity

1. Tom-- (schittli)

   added

   Needs-TriageThe issue is new and needs to be triaged by a work group.The issue is new and needs to be triaged by a work group.

   on Jan 20, 2022
2. iSazonov commented on Jan 21, 2022

   

   Ilya (iSazonov)

   on Jan 21, 2022

   Last edited by iSazonov

   Collaborator

   More actions

   Conclusion "Won't fix" was made by WG-Cmdlets in Aug,2021 #3607 (comment)

   It seems .Net hasn't plans to implement YAML so close as duplication.

   👍React with 👍1Reacted by gaelcolas
3. Ilya (iSazonov)

   added

   Resolution-DuplicateThe issue is a duplicate.The issue is a duplicate.

   on Jan 21, 2022
4. jhoneill commented on Jan 21, 2022

   

   James O'Neill (jhoneill)

   on Jan 21, 2022

   Last edited by daxian-dbw

   More actions

   To put everything in one place here is what was said in 3607

   @PowerShell/wg-powershell-cmdlets has been discussing this issue, and despite the extremely high demand (and my own personal desire to have strong, canonical YAML cmdlets), we're unfortunately going to have to close it (for now) as Won't Fix. The reasoning is two-fold:

   (1) While the PowerShell package is already fairly large, we're doing our best not to add new dependencies to the package so that we don't continue to grow our size unfettered, and because we believe that pulling modules from the PowerShell Gallery (or an internal trusted Gallery, having been vetted appropriately by an enterprise) should be a standard part of a PS7 workflow.
   (2) As a team, we simply don't have the capacity to build a .NET YAML parser from scratch, nor do we have the capacity to vet, support, and service a 3rd party library for which the security implications are high-stakes.
   If .NET were to officially support a YAML library, we (as Microsoft) could potentially look into supporting a YAML module on the Gallery. But until that point, the existing community modules will have to suffice.

   The community module referred to has been downloaded 18 million times. It is based on YamDotNet has been download from Nuget 36 Million times. But as the quote above says the team don't have the capacity to "vet support and service" it (I'm not sure what happened with NewonSoftJson before .NET added native JSON support).

   We have a classic case of different Microsoft teams ignoring each other .

   • Azure Pipelines team YAML Is new and shiny let's be the first to use it!!! BTW despite the title Azure generally uses JSON and only pipelines use YAML.
   • PowerShell team Customers want us to do more things than Microsoft gives resource for. We can't write parsers for JSON, XML, YAML etc. (or validate 3rd party ones) we need .NET to do that. A module which uses a community parser needs to be a community module.
   • .NET team We don't see the need to support every markup as it is invented, and there are good community libraries.

   and customers like the OP say they don't want "community" stuff they want everything to come from Microsoft. (Though from the use of "M$" I assume the OP doesn't like paying for it).

   👍React with 👍8Reacted by Luke Boening, Jordan Borean, lukeb1961, Aurimas Navardauskas, Alex Harper, Dongbo Wang, Vaccano and Andrey Tomilin
6. ghost closed this as completedon Jan 22, 2022