forked from cloudfoundry/cf-deployment-concourse-tasks
-
Notifications
You must be signed in to change notification settings - Fork 0
/
task.yml
37 lines (31 loc) · 1.24 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
---
platform: linux
image_resource:
type: registry-image
source:
repository: cloudfoundry/cf-deployment-concourse-tasks
tag: latest
inputs:
- name: cf-deployment-concourse-tasks
- name: base-ops-files
- name: new-ops-files
outputs:
- name: collected-ops-files
params:
BASE_OPS_FILE_DIR:
# - Optional
# - Directory in the `base-ops-files` input that contains the base ops files
# - If unspecified, input `base-ops-files` will be the root for finding
# the base set of operations files
# - If specified, the path must exist in the base-ops-files resource.
NEW_OPS_FILES:
# - Optional
# - List of paths in the `new-ops-files` input that contains the new ops files
# - If unspecified, every file in the root directory of the input `new-ops-files` will be
# collected - any ops files in subdirectories will not be collected.
# - If specified, each ops file listed will be copied to the `collected-ops-files` output.
# For example, if the path for the ops-file is `new-ops-files/my-env/ops.yml`,
# the user must include `my-env/ops.yml` in the value for `NEW_OPS_FILES`. The path in the output
# will be `collected-ops-files/BASE_OPS_FILE_DIR/ops.yml`.
run:
path: cf-deployment-concourse-tasks/collect-ops-files/task