-
Notifications
You must be signed in to change notification settings - Fork 3
/
.makerc-vars.example
63 lines (48 loc) · 3.4 KB
/
.makerc-vars.example
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
# This is the default configuration file for Catapult
# If you want to change any of the values for yourself define them in the personal/.makerc-personal file
# If you want to change any of the values for your organization/team/project follow the How to customize Catapult section in https://clarifiedsecurity.github.io/catapult-docs/catapult/03-how-to-customize/#customization
# Docker compose project name
# This needs to be unique if you are running multiple Catapult container instances on the same host
MAKEVAR_COMPOSE_PROJECT_NAME :=Catapult
# Timezone for container's /etc/timezone
MAKEVAR_TZ :=UTC
# This starts the SSH service on your host machine
# This required when configuring your host machine with Catapult or configuring VMs that are running on your host machine's VMware Workstation
# Set to true to enable, false to disable
MAKEVAR_ALLOW_HOST_SSH_ACCESS :=false
# If you are not using sudo you can leave this empty, MacOS for an example
MAKEVAR_SUDO_COMMAND :=sudo -E
# This repo is used to store your customizations for Catapult
# Make sure to follow the correct folder and file structure defined in the Catapult README under customization section
# Example for SSH git@github.com:YourAccount/YourProject.git or HTTPS https://github.com/YourAccount/YourProject.git
# Append -b barnch_name to the end of the URL to use a specific branch
MAKEVAR_CATAPULT_CUSTOMIZER_REPO :=
# This is the FQDN of docker registry that is hosting the Catapult container image
# This can be the place where the CI/CD pipelines build your custom Catapult image or your own private registry proxy
# Set the value to the registry machine's FQDN
# Only HTTPS is supported so make sure that you are using a trusted certificates or Catapult trusts your CA (refer to README under customization section)
MAKEVAR_CONTAINER_REGISTRY :=ghcr.io
# This is the name of the Catapult container image that will be used
MAKEVAR_IMAGE_NAME :=clarifiedsecurity/catapult
# This is the image tag of the Catapult container image that will be used
# Available options are latest or staging, or a specific version number listed here https://github.com/ClarifiedSecurity/catapult/pkgs/container/catapult/versions
MAKEVAR_IMAGE_TAG :=latest
# This is Catapult branch or tag that will be used to pull the version of Catapult from the repository
# This also applies to nova.core collection and can be used for private Ansible collections
# Available options are main or staging
MAKEVAR_CATAPULT_VERSION :=main
# Automatically update Catapult, Docker image & custom Ansible collections when new versions are available
# Set to 1 to enable, 0 to disable
MAKEVAR_AUTO_UPDATE :=0
# Setting this to 1 will freeze the update process and will not offer updates to any of the Catapult components
# Use this carefully as you will fall behind the latest updates and it will become increasingly difficult to update Catapult at a later date
MAKEVAR_FREEZE_UPDATE :=0
# This is the webhook URL for Slack or Mattermost where you'll start receiving notifications about the deployment start and end
# Define the URL to enable notifications
MAKEVAR_WEBHOOK_URL :=
# This is the username that will be used to send notifications to Slack or Mattermost
MAKEVAR_WEBHOOK_USERNAME :=Catapult
# This is the channel that will be used to send notifications to Slack or Mattermost
# Use channelname for sending notifications to a channel or @username for sending to a notifications user
MAKEVAR_WEBHOOK_CHANNEL :=
# TEMPLOOKUPFLAG