| MSantos | |
| Feb 10 2021, 4:44 PM |
| F34167644: Maps architecture-High level architecture(4).png | |
| Mar 18 2021, 9:56 AM |
| F34123717: Maps architecture-High level architecture.png | |
| Feb 26 2021, 1:51 PM |
Description: https://tegola.io/
Timeline: Q4
Diagram: See the following section
Technologies: golang
Point person: @MSantos and @Jgiannelos
For now, this is a placeholder while the service is being evaluated internally by the #product-infrastructure-team-backlog
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | akosiaris | T274390 New Service Request tegola-vector-tiles | |||
| Resolved | Jgiannelos | T275874 Create helm charts for tegola vector tile server | |||
| Resolved | None | T283049 Swift account to store pre-rendered vector-tiles | |||
| Resolved | None | T283159 Deploy tegola-vector-tiles to kubernetes |
Please excuse the drive-by comment; from the diagram below it seems that RO access to swift from users and applications happens by talking directly to swift (?) If that's the case I think for accountability and countermeasures (e.g. policy, rate limit, etc) reasons it'd be good to have swift RO access be proxied through the HTTP router, what do you think ?
Hey @fgiunchedi, thanks for the feedback. I think what we are trying to show in the charts is the differentiation between "read-only" and "read-write" access. I will update the chart so we can address the topic you raised.
tegola has been deployed for some time now, so I am resolving this. Feel free to reopen.