Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add upgrade guide for Azure Table Storage v6 #6291

Merged
merged 4 commits into from
Nov 7, 2023
Merged

Conversation

andreasohlund
Copy link
Member

No description provided.

@andreasohlund andreasohlund self-assigned this Nov 1, 2023
@andreasohlund
Copy link
Member Author

@lailabougria @danielmarbach @abparticular This change originated in Particular/NServiceBus.Persistence.AzureTable#670 do you have any input on what we should tell the customer to do if they are using the compatibility mode?

@danielmarbach
Copy link
Contributor

@andreasohlund I have tried to gather as much context with @kentdr in Particular/NServiceBus.Persistence.AzureTable#836

But the gist of this is that the compatibility mode has been around from v3 and has gone through all the required steps so that it can be removed. At the time, we concluded that Azure Table persistence is a bit of a niche and the customers that are using it are used to the cadence of upgrading through the versions because they depend on the storage table APIs that have been constantly evolving over the years. We didn't find it necessary to write a "migration tool" but some of these decisions also predate some of our never policies. I would suggest using the issue Particular/NServiceBus.Persistence.AzureTable#836 to capture feedback over time

@andreasohlund andreasohlund marked this pull request as ready for review November 6, 2023 08:29
@andreasohlund andreasohlund merged commit a4d3089 into master Nov 7, 2023
4 checks passed
@andreasohlund andreasohlund deleted the upgrade-guide-ast branch November 7, 2023 07:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants