azure-powershell
azure-powershell copied to clipboard
Bug fix: "Get-AzAutomationJob fails for some jobIds"
Description
Get-AzAutomationJob failed for some jobIds with the error - "Conversion from JSON failed with error: Unexpected character encountered while parsing value: D. Path '', line 0, position 0." The bug was specific to Powershell 7 and was occurring due to ConvertFrom-Json not identifying strings without quotes around them
Checklist
- [x] Check this box to confirm: I have read the Submitting Changes section of
CONTRIBUTING.mdand reviewed the following information:
- SHOULD select appropriate branch. Cmdlets from Autorest.PowerShell should go to
generationbranch. - SHOULD make the title of PR clear and informative, and in the present imperative tense.
- SHOULD update
ChangeLog.mdfile(s) appropriately- For any service, the
ChangeLog.mdfile can be found atsrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md - A snippet outlining the change(s) made in the PR should be written under the
## Upcoming Releaseheader in the past tense. Add changelog in description section if PR goes intogenerationbranch. - Should not change
ChangeLog.mdif no new release is required, such as fixing test case only.
- For any service, the
- SHOULD have approved design review for the changes in this repository (Microsoft internal only) with following situations
- Create new module from the scratch
- Create new resource types which are not easy to conform to Azure PowerShell Design Guidelines
- Create new resource type which name doesn't use module name as prefix
- Have design question before implementation
- SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
- SHOULD have proper test coverage for changes in pull request.
- SHOULD NOT introduce breaking changes in Az minor release except preview version.
- SHOULD NOT change version of module in pull request
Thank you for your contribution Ab0907! We will review the pull request and get back to you soon.
@Ab0907 please resolve the conflict in ChangeLog.md that's blocking CI. Also, join Azure orgnization by https://aka.ms/AzureGitHub
Joined Azure org and conflict blocking CLI has been resolved
Used AzurePSCmdlet.PowerShellVersion property to avoid duplication.
/azp run azure-powershell - security-tools
Azure Pipelines successfully started running 1 pipeline(s).