Bump Akka.Persistence.Azure from 0.8.3 to 1.5.1

[dependabot]

Bumps Akka.Persistence.Azure from 0.8.3 to 1.5.1.

Release notes

Sourced from Akka.Persistence.Azure's releases.

Akka.Persistence.Azure v1.5.1

1.5.1 March 16 2023

• Update Akka.NET v1.5.1
• Bump Azure.Storage.Blobs to 12.15.0
• Add multi journal support

Multi Journal Support

You can now add more than one Akka.Persistence.Azure settings and use them singularly for different Akka plugins.

In the example below, we set up two separate journal options with two distinct identifier, one is being used as default persistence plugin, and the other are being used as the journal for cluster sharding.

var persistenceJournal = new AzureTableStorageJournalOptions(true)
{
    Identifier = "azure-journal",
    ConnectionString = connectionString
};
var shardJournal = new AzureTableStorageJournalOptions(false)
{
    Identifier = "azure-shard-journal",
    ConnectionString = shardConnectionString
};
builder
    .WithClustering()
    .WithAzureTableJournal(persistenceJournal)
    .WithAzureTableJournal(shardJournal)
    .WithAzureBlobsSnapshotStore(new AzureBlobSnapshotOptions
    {
        ConnectionString = connectionString
    })
    .WithShardRegion<ShardRegionKey>(
        "region-1",
        Customer.Props,
        new MessageExtractor(10),
        new ShardOptions
        {
            JournalOptions = shardJournal,
            StateStoreMode = StateStoreMode.Persistence
        });

Changes:

• 346e02858547a1fc8158b739ed45c020d0ea2d11 Update RELEASE_NOTES.md for 1.5.1 release (#295)
• 0d9fbcd2ccd819aad180ca8a376a4d682724d702 Bump AkkaVersion from 1.5.0 to 1.5.1 (#294)
• 51254a9ae1a4254a70985e3d60f9c2eb98104e41 Update copyright headers to 2023 (#292)
• 05368d5723a5d45bbf946c69221657e0b9f8d7d0 Multi journal config feature implementation (#272)
• 4bc801e0ea06d495324b7f529c50af28592d0291 Bump Azure.Storage.Blobs from 12.13.1 to 12.15.0 (#287)

... (truncated)

Changelog

Sourced from Akka.Persistence.Azure's changelog.

1.5.1 March 16 2023

• Update Akka.NET v1.5.1
• Bump Azure.Storage.Blobs to 12.15.0
• Add multi journal support

Multi Journal Support

You can now add more than one Akka.Persistence.Azure settings and use them singularly for different Akka plugins.

In the example below, we set up two separate journal options with two distinct identifier, one is being used as default persistence plugin, and the other are being used as the journal for cluster sharding.

var persistenceJournal = new AzureTableStorageJournalOptions(true)
{
    Identifier = "azure-journal",
    ConnectionString = connectionString
};
var shardJournal = new AzureTableStorageJournalOptions(false)
{
    Identifier = "azure-shard-journal",
    ConnectionString = shardConnectionString
};
builder
    .WithClustering()
    .WithAzureTableJournal(persistenceJournal)
    .WithAzureTableJournal(shardJournal)
    .WithAzureBlobsSnapshotStore(new AzureBlobSnapshotOptions
    {
        ConnectionString = connectionString
    })
    .WithShardRegion<ShardRegionKey>(
        "region-1",
        Customer.Props,
        new MessageExtractor(10),
        new ShardOptions
        {
            JournalOptions = shardJournal,
            StateStoreMode = StateStoreMode.Persistence
        });

1.5.0 March 02 2023

• Targets Akka.NET v1.5.0
• Targets Akka.Hosting v1.5.0

0.9.2 September 27 2022

• Bump Akka.NET version from 1.4.40 to 1.4.43

... (truncated)

Commits

• 346e028 Update RELEASE_NOTES.md for 1.5.1 release (#295)
• 0d9fbcd Bump AkkaVersion from 1.5.0 to 1.5.1 (#294)
• 51254a9 Update copyright headers to 2023 (#292)
• 05368d5 Multi journal config feature implementation (#272)
• 4bc801e Bump Azure.Storage.Blobs from 12.13.1 to 12.15.0 (#287)
• abfb60b Fix NuGet URL, license, and icon url (#291)
• 899b232 upgraded Akka.Persistence.Azure to Akka.NET v1.5 (#290)
• 1c912b9 Bump Docker.DotNet from 3.125.12 to 3.125.13 (#289)
• 4df4bb0 Update Akka.NET and Akka.Hosting to 1.5.0-beta6 (#288)
• 5f234cb Bump Microsoft.NET.Test.Sdk from 17.4.1 to 17.5.0 (#286)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)