-
Notifications
You must be signed in to change notification settings - Fork 76
/
task.yml
74 lines (62 loc) · 2.04 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
---
platform: linux
image_resource:
type: registry-image
source:
repository: cloudfoundry/cf-deployment-concourse-tasks
tag: latest
inputs:
- name: cf-deployment-concourse-tasks # - This repo
- name: bbl-state # - The env repo containing the Director's bbl state dir
- name: pool-lock
optional: true
outputs:
- name: updated-bbl-state
# - The bbl-state resource, with changes git committed,
# ready to be `put` to a git resource.
# - This output _must_ be persisted for these tasks to function properly
run:
path: cf-deployment-concourse-tasks/bbl-destroy/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
GIT_COMMIT_EMAIL: "cf-release-integration@pivotal.io"
GIT_COMMIT_USERNAME: "CI Bot"
# - Optional
# - You may choose the git committer username and email address by setting these
# AWS Configuration Params
# - Required for AWS
BBL_AWS_ACCESS_KEY_ID:
BBL_AWS_SECRET_ACCESS_KEY:
# Azure Configuration Params
# - Required for Azure
BBL_AZURE_CLIENT_ID:
BBL_AZURE_CLIENT_SECRET:
BBL_AZURE_TENANT_ID:
BBL_AZURE_SUBSCRIPTION_ID:
# GCP Configuration Params
# - Required for GCP
BBL_GCP_SERVICE_ACCOUNT_KEY:
# - Key content or path to the file containing credentials downloaded from GCP
# - Path is relative to the `bbl-state` input
# OpenStack Configuration Params
# - Required for OpenStack
BBL_OPENSTACK_AUTH_URL:
BBL_OPENSTACK_AZ:
BBL_OPENSTACK_NETWORK_ID:
BBL_OPENSTACK_NETWORK_NAME:
BBL_OPENSTACK_PASSWORD:
BBL_OPENSTACK_USERNAME:
BBL_OPENSTACK_PROJECT:
BBL_OPENSTACK_DOMAIN:
BBL_OPENSTACK_REGION:
STORE_BBL_STATE_AS_TARBALL: false
# - Optional
# - Creates a tarball of the bbl-state directory, instead of treating it
# - as a git repo and committing.
# - This is useful if you want to store your state file in S3 or GCS.
BBL_JSON_CONFIG:
# - Optional
# - For if you need a dynamic config for BBL