-
Notifications
You must be signed in to change notification settings - Fork 1
/
.env
67 lines (54 loc) · 2.68 KB
/
.env
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
# note: If you add values here, ensure they're also added to
# deploy_urbanos.yml / teardown_urbanos.yml as well as the repo actions
# environment
# Auth0 User API Key, pulled from user metadata. Used to connect to disc-streams
# by "streams-to-eventhub"
AUTH0_USER_API_KEY=""
# links andi to auth0
JUNO_ANDI_AUTH0_CLIENT_SECRET=""
# The azure subscription that resources will be deployed to
# `az ad sp create-for-rbac --role="Contributor" --scopes="/subscriptions/{subscription_id}"`
JUNO_AZURE_SUB_ID=""
JUNO_DEMO_AZURE_APP_ID=""
JUNO_DEMO_AZURE_PASSWORD=""
JUNO_DEMO_AZURE_TENANT=""
AZURE_RESOURCE_GROUP_NAME=""
# If these are ommited, a local state file will be used instead of terraform.io
# for remote state.
# https://app.terraform.io/app/settings/tokens (user scope)
JUNO_DEMO_TF_BACKEND_KEY=""
JUNO_DEMO_TF_WORKSPACE_NAME=""
JUNO_DEMO_TF_ORGANIZATION_NAME=""
# The value of a domain that has been registered with Azure nameservers, and
# has a created dnszone on the resource group shared by the cluster.
JUNO_DOMAIN_NO_SUFFIX="cooldomain"
JUNO_DOMAIN_WITH_SUFFIX="cooldomain.com"
# if populated, streams-to-event-hub image will be deployed, which relays
# a streams topic created in "initialize-andi" gh action step
# into this provided event hub url
JUNO_EVENT_HUB_URL=""
# used to connect raptor to auth0. Many UrbanOS services use raptor to validate
# user info.
JUNO_RAPTOR_AUTH0_CLIENT_SECRET=""
# used to tag resources. It must be unique from other users deploying juno
# terraform, so that there are no resource conflicts if multiple deployments
# are using the same subscription. Choose a unique name.
JUNO_RESOURCE_PREFIX=""
# if set to "true", cert manager will use staging lets encrypt instead of prod.
# staging certs undergo the same service validations, and are valid https connections,
# but are issued from an untrusted CA. Prod certs have rate limits.
# Staging is best for testing, to avoid approaching weekly prod rate limits.
# You'll need to manually trust the staging CA to view the resulting sites.
# prod letsencrypt usage limits: https://letsencrypt.org/docs/rate-limits/
# staging usage limits: https://letsencrypt.org/docs/staging-environment/
# not included in github environemnt secrets, since it's specified in workflow
# kickoff.
JUNO_USE_STAGING_LETS_ENCRYPT="false"
# Will deploy Sauron if enabled
# https://github.com/UrbanOS-Public/charts/tree/master/charts/sauron
JUNO_ENABLE_SAURON="false"
# Github token for Sauron so it can pull latest smartcitiesdata apps
JUNO_SAURON_GITHUB_PAT=""
# Version of the urbanos_chart to use. See https://github.com/UrbanOS-Public/charts.
# Can be used to keep demo pinned to older releases.
URBANOS_CHART_VERSION=""