You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Align MigrateFromNamedSingleTopic obsolete version range (#1209)
* Align MigrateFromNamedSingleTopic obsolete version range with the other obsoletes since that is an oversight from a bumping PR.
Introduces also constants for the version range with comments to better indicate the intent.
* Use constants in MigrationTopology class also
---------
Co-authored-by: Daniel Marbach <[email protected]>
Co-authored-by: Brandon Ording <[email protected]>
Copy file name to clipboardExpand all lines: src/Tests/ApprovalFiles/APIApprovals.Approve.approved.txt
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -121,7 +121,7 @@ namespace NServiceBus
121
121
public static NServiceBus.Transport.AzureServiceBus.MigrationTopology MigrateFromNamedSingleTopic(string topicName) { }
122
122
[System.Obsolete(@"The migration topology is intended to be used during a transitional period, facilitating the migration from the single-topic topology to the topic-per-event topology. The migration topology will eventually be phased out over subsequent releases. Should you face challenges during migration, please reach out to |https://github.com/Particular/NServiceBus.Transport.AzureServiceBus/issues/1170|. Will be treated as an error from version 7.0.0. Will be removed in version 8.0.0.", false)]
123
123
public static NServiceBus.Transport.AzureServiceBus.MigrationTopology MigrateFromSingleDefaultTopic() { }
124
-
[System.Obsolete(@"The migration topology is intended to be used during a transitional period, facilitating the migration from the single-topic topology to the topic-per-event topology. The migration topology will eventually be phased out over subsequent releases. Should you face challenges during migration, please reach out to |https://github.com/Particular/NServiceBus.Transport.AzureServiceBus/issues/1170|. Will be treated as an error from version 6.0.0. Will be removed in version 7.0.0.", false)]
124
+
[System.Obsolete(@"The migration topology is intended to be used during a transitional period, facilitating the migration from the single-topic topology to the topic-per-event topology. The migration topology will eventually be phased out over subsequent releases. Should you face challenges during migration, please reach out to |https://github.com/Particular/NServiceBus.Transport.AzureServiceBus/issues/1170|. Will be treated as an error from version 7.0.0. Will be removed in version 8.0.0.", false)]
125
125
public static NServiceBus.Transport.AzureServiceBus.MigrationTopology MigrateFromTopicHierarchy(string topicToPublishTo, string topicToSubscribeOn) { }
126
126
[System.Obsolete("Use `TopicTopology.MigrateFromNamedSingleTopic(string topicName)` instead. The me" +
127
127
"mber currently throws a NotImplementedException. Will be removed in version 6.0." +
* The idea behind obsoleting the migration topology is to make it clear in the user's code base that eventually the migration topology will be removed.
192
+
* The intent was to give users at least two major versions that are aligned with .NET LTS versions time, which should be roughly 2 years to migrate away
193
+
* from the migration topology to the new topic-per-event topology. Should an out-of-band major release be required, consider bumping the `TreatAsErrorFromVersion`
194
+
* and `RemoveInVersion` values to make sure more or least two years have passed after the release v5.0.0 of the transport. It might also be worthwhile
195
+
* checking the linked issue in the obsolete message to see if there are any signals that warrant moving this even further.
196
+
*/
197
+
internalconststringTreatAsErrorFromVersion="7";
198
+
199
+
internalconststringRemoveInVersion="8";
200
+
190
201
internalconststringObsoleteMessage=
191
202
"The migration topology is intended to be used during a transitional period, facilitating the migration from the single-topic topology to the topic-per-event topology. The migration topology will eventually be phased out over subsequent releases. Should you face challenges during migration, please reach out to |https://github.com/Particular/NServiceBus.Transport.AzureServiceBus/issues/1170|.";
Copy file name to clipboardExpand all lines: src/Transport/EventRouting/TopicTopology.cs
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -46,14 +46,14 @@ public static TopicTopology FromOptions(TopologyOptions options) =>
46
46
/// <summary>
47
47
/// Returns a migration topology using a single topic named <c>bundle-1</c> for <see cref="MigrationTopology.TopicToPublishTo"/> and <see cref="MigrationTopology.TopicToSubscribeOn"/>
/// Returns a migration topology using a single topic with the <paramref name="topicName"/> for <see cref="MigrationTopology.TopicToPublishTo"/> and <see cref="MigrationTopology.TopicToSubscribeOn"/>
0 commit comments