Remove deprecation data in fbc-operations, if present #732
Conversation
This file contains 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
2ba8a94 to
4fba56e
Compare
lipoja
reviewed
Oct 9, 2024
ba23f3d to
e8f6045
Compare
lipoja
reviewed
Oct 15, 2024
e8f6045 to
2924050
Compare
6d511ed to
fdc8f50
Compare
When an operator opts into the FBC fragment workflow, it no longer requires deprecations to be specified in configs/. Deprecations can be handled in fragments. Refers to CLOUDDST-23449
fdc8f50 to
9b0e597
Compare
chandwanitulsi
approved these changes
Oct 28, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When an operator opts into the FBC fragment workflow, it no longer requires deprecations to be specified in configs/. Deprecations can be handled in fragments.
Refers to CLOUDDST-23449