Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
D
Dev-Documentation
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Package registry
Model registry
Operate
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
leap
Dev-Documentation
Repository graph
Repository graph
You can move around the graph by using the arrow keys.
api-update-v4
Select Git revision
Selected
api-update-v4
Branches
4
no-masters
default
protected
connection-setup-fallback-strategy
lilypad-architecture
self_healing
5 results
Begin with the selected commit
Created with Raphaël 2.2.0
26
Nov
12
Aug
5
28
Feb
24
31
Jan
29
23
22
29
Mar
23
12
Jul
28
Jun
17
18
Feb
5
3
2
30
Jan
29
4
Merge branch 'feat/aggregate-tunnel-metrics' into 'no-masters'
no-masters
no-masters
feat: add 005-aggregate-tunnel-metrics.md
Merge branch 'fix/update-v3-endpoints' into 'no-masters'
add sample client cert v3/cert.pem, update api_endpoints.md
Merge branch 'maxb/invite-proposal' into 'no-masters'
Merge branch 'apiv3-diagram' into 'no-masters'
Update api v3 diagram
Add proposal for invite system with storage layer
Replace Lilypad API v3-deployment.png
Merge branch 'future-directions' into 'no-masters'
Merge branch 'deployment-diagram' into 'no-masters'
Update 2 files
Merge branch 'add-bridge-flavors' into 'no-masters'
vpnweb deprecation & beyond tofu proposals
change labels for bridges
Merge branch 'proposal/bridge-flavors' into 'no-masters'
example of bridge transport selection mechanisms
add proposal for bridge flavors
pointer to bonafide
Explain default reasoning for lilypad setup
lilypad-archite…
lilypad-architecture
Merge protocols and ports into one field in eip-service.json. It allows us to restrict the number of valid protocol/network combinations.
api-update-v4
api-update-v4
move proto_port_priority.md to api_specs
self_healing
self_healing
Add initial draft of port/protocol self-healing outline
announce geoip_url in provider.json
describing the setup fallback mechanism with flow charts
connection-setu…
connection-setup-fallback-strategy
add empty md file for charting the client sided fallback strategy while setting up a vpn connection
update example ciphers for api v4
change example ipv6 URL
improve readability of geoservice.json for easier drafting
improve readability of geoservice.json
improve formatting of api_endpoints.md
add v3 geoipservice.json
add proposals for provider.json v4
add example povider.json v3
proposed changes vor eip-service.json v4
add example v3 eip-service.json
add a readme about the available API endpoints used in the provider and gateway setup
Update README.md
Initial commit
Loading