Set-DbaAgentJobOutputFile: Made it more clear that the Job and Step parameters expect names. #9675
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
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.
Made it more clear that the
JobandStepparameters expect names. Also mentioned howStephandles special cases. Closes #9674.Type of Change
Invoke-ManualPester)Commands to test
Out-GridViewdoesn't work on my machine, so it may be prudent to verify that these special cases function as I've said that they do. My tests say that they do.Screenshots
Shamefully, I couldn't get one!
Get-Helpdoesn't seem to show the details of parameters on my machine.Learning
Confirming the step names within an Agent Job are unique was reassuring.