-
Notifications
You must be signed in to change notification settings - Fork 76
/
task.yml
168 lines (141 loc) · 6.61 KB
/
task.yml
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
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
---
platform: linux
image_resource:
type: registry-image
source:
repository: cloudfoundry/cf-deployment-concourse-tasks
tag: latest
inputs:
- name: bbl-state # - The repo containing the Director's bbl state dir
optional: true
- name: toolsmiths-env # - Directory containing Toolsmiths metadata file
optional: true
- name: cf-deployment # - The cf-deployment manifest
- name: ops-files # - Operations files to be made available
optional: true
- name: vars-files # - Variable files to be made available
optional: true
- name: release
# - BOSH release source repo or directory containing a release tarball
# - If the input is a git repository, a dev release will be created from
# this repo and used in the deployment. If the input is a directory
# containing a pre-built release tarball, then the release_tarball_name
# input needs to point at a directory containing a "name" file containing
# the full name of the tarball to be used.
- name: release_tarball_name
optional: true
- name: cf-deployment-concourse-tasks # - This repo
run:
path: cf-deployment-concourse-tasks/bosh-deploy-with-created-release/task
params:
BBL_STATE_DIR: bbl-state
# - Path to the directory containing the `bbl-state.json` file
# - The path is relative to the `bbl-state` input
# - If blank or '.', uses `bbl-state` input as the location for bbl state
# - If the specified path does not exist, it will be created
# - This input and parameter will be ignored if toolsmiths-env is provided
MANIFEST_FILE: cf-deployment.yml
# - Required
# - Filepath to the manifest file within the cf-deployment resource
# - The path is relative to root of the `cf-deployment` input
SYSTEM_DOMAIN:
# - Required unless toolsmiths-env optional input is provided
# - CF system base domain e.g. `my-cf.com`
OPS_FILES:
# - Optional
# - List of operations files to be applied to the manifest
# - Quoted and space-separated
# - Ops will be applied in the order they're listed
# - Paths are relative to root of the `ops-files` input
VARS_FILES:
# - Optional
# - List of variable files to be applied to the manifest
# - Quoted and space-separated
# - Variable files will be applied in the order they're listed
# - Paths are relative to root of the `vars-files` input
REGENERATE_CREDENTIALS: false
# - Optional
# - Delete credentials associated with this deployment from CredHub
# - This allows the credentials to be freshly generated each time
# - This is helpful for testing changes around variable generation
# - Works well with fresh deployments
# - Upgrade deployments are not expected to work with total cred rotation
BUMP_SUBMODULE: ""
# - Optional
# - Set to the path of a submodule you want bumped
# prior to creating the dev release.
# - Also requires that you set `SUBMODULE_BRANCH`
SUBMODULE_BRANCH: ""
# - Ignored unless `BUMP_SUBMODULE` is set
# - Required if `BUMP_SUBMODULE` is set
# - Set to the ref you want the submodule checked out to.
# This ref will be used as an argument to `git checkout`
# when updating your submodule.
DEPLOY_WITH_UPTIME_MEASUREMENTS: false
# - Optional
# - This will measure uptime during the bosh deploy task using [uptimer](https://github.com/cloudfoundry/uptimer)
FAIL_ON_DOWNTIME: false
# - Optional
# - This will cause the task to fail if you are not using the DEPLOY_WITH_UPTIME_MEASUREMENTS flag
# - It will cause the concourse task to fail if you do not have perfect uptime
MEASURE_SYSLOG_AVAILABILITY: false
# - Optional
# - Requires DEPLOY_WITH_UPTIME_MEASUREMENTS to be true.
# - This will measure availability of app syslog drain during deployment.
MEASURE_TCP_AVAILABILITY: false
# - Optional
# - Requires DEPLOY_WITH_UPTIME_MEASUREMENTS to be true.
# - This will measure availability of TCP routing during deployment.
TCP_DOMAIN:
# - Required if MEASURE_TCP_AVAILABILITY or MEASURE_SYSLOG_AVAILABILITY is set to true,
# unless toolsmiths-env is provided. With toolsmiths-env, this value is automatically calculated.
# - Domain used by CF for creating tcp routes to apps, syslog.
# - Usually of the form `tcp.[SYSTEM_DOMAIN]` (e.g. `tcp.my-cf.com`).
TCP_PORT:
# - Required if MEASURE_TCP_AVAILABILITY is set to true.
# - Available port within the 'reservable_ports' range,
# - used to create a tcp route for TCP routing availability measurement.
AVAILABLE_PORT:
# - Required if MEASURE_SYSLOG_AVAILABILITY is set to true.
# - Available port within the 'reservable_ports' range,
# - used to create a tcp route for the syslog availability measurement.
APP_PUSHABILITY_THRESHOLD: 0
# - Optional
# - This sets the maximum number of allowed uptimer failures for app pushability
# - The default threshold value of 0 is our working value for cf-deployment, and is likely to be updated
APP_STATS_THRESHOLD: 0
# - Optional
# - This sets the maximum number of allowed uptimer failures for app stats
# - The default threshold value of 0 is our working value for cf-deployment, and is likely to be updated
HTTP_AVAILABILITY_THRESHOLD: 0
# - Optional
# - This sets the maximum number of allowed uptimer failures for http availability
# - The default threshold value of 0 is our working value for cf-deployment, and is likely to be updated
TCP_AVAILABILITY_THRESHOLD: 0
# - Optional
# - This sets the maximum number of allowed uptimer failures for tcp availability
# - The default threshold value of 0 is our working value for cf-deployment, and is likely to be updated
RECENT_LOGS_THRESHOLD: 0
# - Optional
# - This sets the maximum number of allowed uptimer failures for recent logs
# - The default threshold value of 0 is our working value for cf-deployment, and is likely to be updated
STREAMING_LOGS_THRESHOLD: 0
# - Optional
# - This sets the maximum number of allowed uptimer failures for streaming logs
# - The default threshold value of 0 is our working value for cf-deployment, and is likely to be updated
APP_SYSLOG_AVAILABILITY_THRESHOLD: 0
# - Optional
# - This sets the maximum number of allowed uptimer failures for app syslog availability
# - The default threshold value of 0 is our working value for cf-deployment, and is likely to be updated
USE_SINGLE_APP_INSTANCE: false
# - Optional
# - Configures uptimer to deploy with a single app instance rather than two.
# - This is primarily used by Diego to validate new uptime features.
BOSH_DEPLOY_ARGS:
# - Optional
# - Supplies additional arguments to the bosh deploy command
# - For example, '--recreate'
BOSH_LITE: false
# - Optional
# - Used to determine whether we should upload a warden stemcell
# - Boolean