-
Notifications
You must be signed in to change notification settings - Fork 0
/
values.yaml
83 lines (67 loc) · 2.99 KB
/
values.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
# Default values for github-integration-chart.
# This is a YAML-formatted file.
app:
# Set true to install the app and the auth proxy
enabled: false
# Port at which the app will be accessed
nodePort: 30080
# Where to access i3dhub.
# In case instant3Dhub.enabled, this should be one of the instant3Dhub.entrypoints
hubURL: http://localhost:30042
# Auth proxy config
authProxy:
url: http://localhost:30081/authenticate
nodePort: 30081
# Github repo name
repositoryName: "Your_Repository_Name"
# Github clientID
clientId: Your_Client_ID
# Github client secret
clientSecret: Your_Client_Secret
# Where to redirect after successful login
redirectURL: http://localhost:30080/login
# instant3Dhub config
instant3Dhub:
# Set true to install instant3Dhub
enabled: false
# Where to access the license server
licenseServer: http://license.threedy.io:8200
# Storage class which will provide the persistence volumes
storage.class: hostpath
# i3dhub entry points
entrypoints: [http://localhost:30042]
# Registry where i3dhub images are available
registry: images.threedy.io
# Configure options relating to required authorization headers and caching.
auth:
# Set any authorization header names which must be passed to data backends.
# These will be copied from incoming client requests and used while downloading
# data or performing authorization requests against the backends.
# No client headers or cookies will be forwarded to any backends by default as
# this could leak client credentials to arbitrary URLs.
# If dataGateways are defined, forwardHeaders or forwardCookies fields can also be
# defined there on a per-rule basis. This should be preferred as it is more robust
# than regex matching URLs.
# In either case, rules from URN definitions are applied first, after which the
# regex rules defined here are applied on the URL generated by resolving the URN.
forwardHeaders:
- match: "http://i3dhub-github-gateway-service:8090/.*"
headers: [ "Authorization"]
# Sets a list of headers to include in any Access-Control-Allow-Headers preflight
# responses. This is required when setting headers manually via the webvis-API.
# For example, if clients are required to attach credentials not in cookie form,
# the specfic headers must be allowed here.
clientHeaders:
- "Authorization"
#- "X-Requested-With"
# Set the URN mapping rules per data gateway. See the integration documentation for
# motivation and concepts behind data gateways and URN mappings.
#
# For templates, $(n) is the n-th value in the URN separated after urn:namespace:specifier:xxx
# e.g.: urn:x-i3d:shape:sphere ($(1) == sphere)
dataGateways:
defaultGateway:
- namespace: github
specifier: 3d-data
urlContentType: [ openjt , step , stp , x3d-xml , step.ap203 ]
urlTemplate: http://i3dhub-github-gateway-service:8090/githubFile/$(1)/$(2)/$(3).$(4)