pp-entity-attribute: single apply-scaffold post-action - #147
Open
zekelinAlex wants to merge 1 commit into
Open
Conversation
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.
pp-entity-attribute had seven post-action PowerShell scripts hand-patching Entity.xml and Solution.xml, which is where most of the scaffold flakiness (and the scaffold lock) came from. they're replaced by a single ApplyScaffold.ps1 that calls
txc workspace component apply-scaffoldonce and lets the CLI run all mutations in-process through the metadata library.rendered .template.temp files stay as the payload, cleanup of the temp folders is folded into the same script. template.json goes from seven postActions to one.
depends on TALXIS/tools-cli#187 - the post-action needs a CLI release that has apply-scaffold.