feat: support default outputs pipelines for backwards compatibility #3561
Conversation
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.
Motivation
Output pipelines allow admins to customise how datasets are served to the users, common pipelines are
color-rampto convert elevation data into RGBA orterrain-rgbto convert elevation to terrain-rgbIf there is only one output pipeline, then it will be picked as the default option for the tile, so all endpoints will assume the use of the pipeline.
If a second pipeline is added, the first link will now be broken as there is no default for the system to choose
Modifications
Adds a
default: booleanoption to the pipeline outputs to allow admins to configure what the default pipeline isVerification
unit tests.