Add --what-if option to resource set command for previewing changes#1333
Open
Gijsreyn wants to merge 4 commits intoPowerShell:mainfrom
Open
Add --what-if option to resource set command for previewing changes#1333Gijsreyn wants to merge 4 commits intoPowerShell:mainfrom
--what-if option to resource set command for previewing changes#1333Gijsreyn wants to merge 4 commits intoPowerShell:mainfrom
Conversation
--what-if option to resource set command for previewing changes
…into PowerShellgh-566/main/support-whatif-resource
Collaborator
|
@Gijsreyn - if you feel like resolving the merge conflicts on this, I will review! |
Collaborator
Author
|
@tgauth - hey Tess, should be good to go with the merge conflicts (there are none) :) |
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
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.
PR Summary
This PR adds support for
--what-ifmode when invoking a resource'ssetoperation directly via the CLI.PR Context
Fix #566.