Repository navigation
feat: add a shigola map provider in a new retiler v3 schema (MAPCO-11992) - #184
Open
shimoncohen wants to merge 2 commits into
Open
shimoncohen wants to merge 2 commits into
shimoncohen wants to merge 2 commits into
Conversation
app.map.provider gains shigola, in which retiler sends each metatile's bbox
to shigola's Cache Admin API instead of fetching a map. Its app.map.shigola
block takes the operation (purge by default, or seed), the targets as
{map, layers?} (layers refused for a seed, as shigola seeds whole maps only),
optional tile matrix sets and token, and the request timeout (70000 ms by
default, above shigola's own 60 s request timeout).
app.map.shigola is required with the shigola provider, and app.map.wms only
with the others.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Released schemas are not modified, so v2 is restored as released and the shigola provider ships as retiler v3. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Contributor
|
Hi it is me, your friendly bot helper! 👋 {
"dependencies": {
"@map-colonies/schemas": "https://ghatmpstorage.blob.core.windows.net/npm-packages/schemas-4cc694c41b5f8143b876ed71e7296658d8518326.tgz"
}
}The link will expire in a week ⌛ |
This branch has not been deployed
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.
Reopened from #181 (by @NivGreenstein), which was auto-closed by an accidental force-push on 2026-10-20. Review history is on #181.
Adds a
shigolamap provider in a new retiler v3 schema, for MAPCO-11992. Released schemas aren't modified (the changed-schemas check enforces this), so v3 is v2 plus the changes below, and v2 is untouched. In this mode retiler sends each metatile's bbox to Shigola's Cache Admin API instead of fetching a map.Changes from v2, all additive (a v2 config is a valid v3 config)
app.map.providergainsshigola.app.map.shigolablock:operation:purge(default) orseed.targets:[{ map, layers? }]. Layers are refused for a seed, since Shigola seeds whole maps only.tileMatrixSets: optional.token: optional.timeoutMs: defaults to 70000, above Shigola's own 60 s request timeout.app.map.shigolais required with theshigolaprovider, andapp.map.wmsis now only required with the others.Verified:
npm run validatepasses. Valid Shigola configs (purge with layers, seed without them) and the existing WMS default are accepted; a seed with layers, missing targets and an unknown target key are rejected.Needed by MapColonies/retiler#42. That PR can't pass CI until this is released and retiler is bumped to it.
🤖 Generated with Claude Code
🤖 Generated with Claude Code