migrate limelight aliases to follow new pattern #3183
Merged
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.
This PR migrates limelight alias to use new pattern. This streamlined method for creating an alias in Prebid Server eliminates the code needed to create an alias and relies on just one configuration file.
The configuration file now contains only essential information for alias creation, with all other details derived from its parent.
Testing details:
Following are the alias of limelight digital
/info/bidders/[bidder-name]
returns response for all aliases
/info/bidders
response include all aliases of limelight digital
/cookie_sync
Bidder info yaml defines syncer only for evtech bidder. As shown below endpoint returns iframe syncer cfg in response