fix: set JBDA feeds to published on import#1615
Merged
davidgamez merged 1 commit intomainfrom Mar 9, 2026
Merged
Conversation
cka-y
approved these changes
Mar 9, 2026
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
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.
Summary:
This PR set the operational_status to published on imported feeds from jbda source. For historical reasons, the operational status was set to WIP while importing due to the delayed process of making all JBDA feeds available; this is not the case anymore.
Expected behavior:
The operational status for the newly created JBDA feeds is set to published.
Testing tips:
Execute the JBDA script in DEV and verify that the operational status for the newly created feeds is set to published.
Please make sure these boxes are checked before submitting your pull request - thanks!
./scripts/api-tests.shto make sure you didn't break anything