Conversation
tznind
changed the title
jas88
approved these changes
Nov 18, 2021
Contributor
|
While MigrateUsages property in the pipeline is functional additional work required with DLS team to make sure all users needs are met. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prior to this PR when updating a cohort there was a setting
Deprecate Old Cohort On Successwhich defaulted to true. However just because a cohort was deprecated on an ExtractionConfiguration you could still extract it.This PR contains 2 features:
'Migrate Usages' is disabled by default to preserve backwards compatibility and because the Deprecated status check removes the risk of releasing the wrong cohort.
Fixes #650
IsDeprecated Fix:
Migrate Usages:
