[AB#40568] channel id changed in catalog service to match other entities #104
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
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.
Pull Request
Prerequisites
Description
To match other entities, channel ID is now explicitly adjusted in catalog service, adding a
channel-prefix to the original UUID value. Corresponding changes are made in the entitlement service to support this. And explicit database migration is added to update possible existing channel entries in the channel service database.Testing Notes
Publish a channel, make sure that catalog API would return a valid id value (e.g.
channel-92b27f89-ac27-4e50-8fe7-e4cd75a5855e) when querying channels and channel images. IF VOD-to-live service is configured to enable DRM protection - make sure that passing the updated channel id to theentitlementendpoint would return the entitlement token.