Remove dependency on powershell-yaml. Closes #47#50
Merged
fireflycons merged 9 commits intomasterfrom Oct 6, 2019
Merged
Conversation
- Install custom psdeploy (no YamlDotNet conflict) - Move some stuff to /build dir
- Check for installation success - Explicit import in build.ps1
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
All reading and writing of YAML is done via YamlDoTnet directly, with the exception of
New-PSCFNPackagewhere a template format flip is often implied. This depends oncfn-flipbeing present until I can work out how to do short-from intrinsics as custom tags in YAML.Also introduces a custom build of RamblingCookieMonster/PSDeploy#130 that uses the same version of YamlDotNet as this (until he merges my PR), so as not to create DLL hell.