feat: Added "Set Entities" script for Azure Table storage

[Annelotte-Mons]

Added new "AzTable-SetEntities" script.

This script will first connect to the specified Azure Storage Account / Table.
Then it will first delete all existing entities on the specified table.
Finally it will insert new entities based on a JSON configuration file.

An example of this configuration file looks like:

{
  "entities": [
    {
      "PartitionKey": "RDS-Fileshare",
      "Active": "Yes",
      "Domain": "Truck",
      "Service": "TruckOrder-UpdateConfirmation",
      "Action": "Process",
      "Version": "v1",
      "ContentType": "text/xml",
      "MinimumFileAgeInSeconds": "60",
      "Recursive": "No",
      "Sender": "Truckers",
      "ServerDirectory": "/Truckers/orders/in",
      "ServerId": "RDS-Fileshare"
    },
    {
      "PartitionKey": "RDS-Fileshare",
      "Active": "Yes",
      "Domain": "Messaging",
      "Service": "STM",
      "Action": "RoutingSlipIngest",
      "Version": "v2",
      "ContentType": "text/plain",
      "MinimumFileAgeInSeconds": "60",
      "Recursive": "No",
      "Sender": "Truckers",
      "ServerDirectory": "/Truckers/STM/in",
      "ServerId": "RDS-Fileshare"
    }
  ]
}``

The fields PartitionKey & RowKey are optional, if not provided a random GUID will be used.
Other fields can be any key-value you'd like, 

Script uses 'AzTable' module

[netlify]

✅ Deploy Preview for arcus-scripting ready!

Name	Link
🔨 Latest commit	01058af
🔍 Latest deploy log	https://app.netlify.com/sites/arcus-scripting/deploys/64770d34e8d64600087516b6
😎 Deploy Preview	https://deploy-preview-222--arcus-scripting.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[Annelotte-Mons]

Todo: Add docs? If so, what folder/files exactly?

[mbraekman]

Haven't had a thorough look yet, but can you:

• make sure to change the name of the command to use the approved verbs -> see docs
  This should align with the existing commands, for example: Set-AzStorageTableEntities instead of AzTable-SetEntities.
• add documentation, see the contribution guide on how/where.
• include some unit/integration tests, as per the existing test-projects.

If anything is unclear, let us know and we'll point you in the right direction!

By default this script is going to delete all entities and add those configured in the JSON-file. Would it be an idea to use a switch-param to indicate whether the existing entries should be removed? This way this can be created to simply add new entries as well?

[stijnmoreels]

Great stuff! Thanks for your PR! 🎉
Like Maxim said: maybe a quick rundown of our contribution guide will already help you a lot. I'll also wait for my review. Please contact us if you're having trouble with something.

Thanks again for your enthusiasm!

[stijnmoreels]

Thank you for these changes already! 🎉🎉 Looks great. Super job on providing the necessary logs and error handling for missing resources or values. Will bring great user experience to our library. Much appreciated!

Added some suggestions, but the biggest missing link here are tests (both unit and integration tests).

Unit tests could check for regular success/failure paths, while the integration tests can actually run this functionality against a real storage account. The tests would have to setup/teardown entities before/after running the script to make it stable.
Are you up for this, or should we help out?
I'll first let my buddy @pim-simons have a look at this too.

[pim-simons]

Unit and integration tests have been added, but annoyingly I cannot figure out how to run the DevOps pipeline for this PR 🙈
@stijnmoreels any idea on how to trigger this?

[stijnmoreels]

/azp run CI - Arcus.Scripting

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[stijnmoreels]

Great!

[stijnmoreels]

Unit and integration tests have been added, but annoyingly I cannot figure out how to run the DevOps pipeline for this PR 🙈 @stijnmoreels any idea on how to trigger this?

Triggered it: seems like the built-in PowerShell JSON deserialization expects (always?) a JSON object, while we're testing with arrays.

[pim-simons]

Unit and integration tests have been added, but annoyingly I cannot figure out how to run the DevOps pipeline for this PR 🙈 @stijnmoreels any idea on how to trigger this?

Triggered it: seems like the built-in PowerShell JSON deserialization expects (always?) a JSON object, while we're testing with arrays.

I had the same issue on my machine, had to update the Powershell version to 7.3.4 and the issue was fixed.
It seems the DevOps agents (windows-latest and ubuntu-latest) are running Powershell version 7.2.11, I will look into how to update to the latest version.

[pim-simons]

/azp run CI - Arcus.Scripting

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[pim-simons]

/azp run CI - Arcus.Scripting

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[pim-simons]

/azp run CI - Arcus.Scripting

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[stijnmoreels]

Strange that this pipeline is not triggered automatically. Could it be that the main branch on the PR-branch is still master? 🤔

[pim-simons]

Strange that this pipeline is not triggered automatically. Could it be that the main branch on the PR-branch is still master? 🤔

Not really sure, but at least the tests are now all working correctly and finished successfully 😉

[stijnmoreels]

Super. This looks ready!
Thx for both validation+tests. ❤️