Closed
Bug 1711119
Opened 4 years ago
Closed 4 years ago
Move VPN to automation infrastructure
Categories
(Data Platform and Tools :: General, task)
Data Platform and Tools
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: frank, Assigned: relud)
References
Details
VPN lives entirely in the spoke-default project right now. This has been fine except it limits our ability to use the automation infrastructure to provide new views and explores to the team. There's also been asks about create a shared folder for the VPN project, which the automation infrastructure owns.
This should be relatively straightforward:
- Add vpn to the
custom-namespaces.yamlfile, with names that match the existing deploy (e.g. directory name and model name both match the namespace name and title). - Deploy to Looker. The automation infra will not add any new models, but will then add a directory and
looker-hubmachinery.
In the future, we can then deploy new views and explores for VPN through lookml-generator.
| Reporter | ||
Comment 1•4 years ago
|
||
Relud, is this something you might have the bandwidth to tackle?
Flags: needinfo?(dthorn)
| Assignee | ||
Comment 3•4 years ago
|
||
| Assignee | ||
Comment 4•4 years ago
|
||
| Assignee | ||
Updated•4 years ago
|
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•