GWC REST API fix to fill in the TileLayerInfo blanks when creating a TileLayer #208
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.
To be raised as an issue upstream. Work around the behaivor
mismatch between GWC's REST API and GeoServer's GWC web-ui.
When creating a tile layer with the web-ui, the GeoServerTileLayerInfo
is populated with the defaults from GWCConfig (set in GWCSettings page).
When creating a tile layer through the REST API, it allows a minimal
payload but does not fill in the blanks with the defaults from GWConfig.
e.g., the following payload:
results in an unsusable tile layer:
where from the default tile layer settings it should be more like: