CODEWITHSUNDEEP
jsonpowershell
AnAverageDev
AnAverageDev

Reputation: 143

Reading JSON objects in Powershell

I need to integrate a JSON file which contains paths of the different objects in a PS script that generates and compares the hash files of source and destination. The paths in the JSON file are written in the format that I have stated below. I want to use the paths in that manner and pipe them into Get-FileHash in PowerShell. I can't figure out how to integrate my current PowerShell script with the JSON file that contains the information (File Name, full path) etc.

I have two scripts that I have tested and they work fine. One generates the MD5 hashes of two directories (source and destination) and stores them in a csv file. The other compares the MD5 hashes from the two CSV files and generates a new one, showing the result(whether a file is absent from source or destination).

Now, I need to integrate these scripts in another one, which is basically a Powershell Installer. The installer saves the configurations (path, ports, new files to be made etc etc) in a JSON format. In my original scripts, the user would type the path of the source and destination which needed to be compared. However, I now need to take the path from the JSON configuration files. For example, the JSON file below is of the similar nature as the one I have.

{
"destinatiopath": "C:\\Destination\\Mobile Phones\\"
"sourcepath": "C:\\Source\\Mobile Phones\\"
"OnePlus" : {
"files": [
{
"source": "6T",
"destination: "Model\\6T",
]
}
"Samsung" : {
"files": [
{
"source": "S20",
"destination": "Galaxy\\S20",
}
]

This is just a snippet of the JSON code. It's supposed to have the destination and source files. So for instance if the destination path is: C:\\Destination\\Mobile Phones\\ and the source path is C:\\Source\\Mobile Phones\\ and OnePlus has 6T as source and Model\\6T as destination, that means that the Powershell Installer will have the full path C:\\Destination\\Mobile Phones\\Model\\6T as the destination, and C:\\Source\\Mobile Phones\\6T as the source. The same will happen for Samsung and others.

For now, the MD5 hash comparison PS script just generates the CSV files in the two desired directories and compares them. However, I need to check the source and destination of each object in this case. I can't figure out how I can integrate it here. I'm pasting my MD5 hash generation code below.

Generating hash

#$p is the path. In this case, I'm running the script twice in order to get the hashes of both source and destination. 
#$csv is the path where the csv will be exported. 
Get-ChildItem $p -Recurse | ForEach-Object{ Get-FileHash $_.FullName -Algorithm MD5 -ErrorAction SilentlyContinue} | Select-Object Hash,
    @{
        Name = "FileName";
        Expression = { [string]::Join("\", ($_.Path -split "\\" | Select-Object -Skip ($number))) }
    } | Export-Csv -Path $csv

Upvotes: 1

Views: 3163

Answers (1)

Tomalak
Tomalak

Reputation: 338376

I want to use the paths in that manner and pipe them into Get-FileHash in PowerShell.

As the first step I would reorganize the JSON to be easier to handle. This will make a big difference on the rest of the script.

{
    "source": "C:\\Source\\Mobile Phones",
    "destination": "C:\\Destination\\Mobile Phones",
    "phones": [
        {
            "name": "OnePlus",
            "source": "6T",
            "destination": "Model\\6T"
        },
        {
            "name": "Samsung",
            "source": "S20",
            "destination": "Galaxy\\S20"
        }
    ]
}

Now it's very easy to get all the paths no matter how many "phone" entries there are. You don't even really need an intermediary CSV file.

$config = Get-Content config.json -Encoding UTF8 -Raw | ConvertFrom-Json

$config.phones | ForEach-Object {
    $source_path = Join-Path $config.source $_.source
    $destination_path = Join-Path $config.destination $_.destination

    $source_hashes = Get-ChildItem $source_path -File -Recurse | Get-FileHash -Algorithm MD5
    $destination_hashes = Get-ChildItem $destination_path -File -Recurse | Get-FileHash -Algorithm MD5

    # the combination of relative path and file hash needs to be unique, so let's combine them
    $source_relative = $source_hashes | ForEach-Object {
        [pscustomobject]@{
            Path = $_.Path
            PathHash = $_.Path.Replace($source_path, "") + '|' + $_.Hash
        }
    }
    $destination_relative = $destination_hashes | ForEach-Object {
        [pscustomobject]@{
            Path = $_.Path
            PathHash = $_.Path.Replace($destination_path, "") + '|' + $_.Hash
        }
    }

    # Compare-Object finds the difference between both lists
    $diff = Compare-Object $source_relative $destination_relative -Property PathHash, Path

    Write-Host $diff

    $diff | ForEach-Object {
        # work with $_.Path and $_.SideIndicator
    }
}

Upvotes: 4

Related Questions