-
Notifications
You must be signed in to change notification settings - Fork 15
Expand file tree
/
Copy path.catalog-onboard-pipeline.yaml
More file actions
44 lines (44 loc) · 3.25 KB
/
Copy path.catalog-onboard-pipeline.yaml
File metadata and controls
44 lines (44 loc) · 3.25 KB
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
---
apiVersion: v1
offerings:
# below is an example of a Deployable Architecture (DA) solution
- name: deploy-arch-ibm-hpc-lsf # must match the offering name in the ibm_catalog.json
kind: solution
catalog_id: 0d89ec0d-d39a-494d-ac5b-9d940d8cc65f
offering_id: 1444e20a-af22-40d1-af98-c880918849cb
# list all of the variations (flavors) you have included in the ibm_catalog.json
variations:
- name: Cluster-with-LSF
mark_ready: false # have pipeline mark as visible if validation passes
install_type: fullstack # ensure value matches what is in ibm_catalog.json (fullstack or extension)
destroy_resources_on_failure: false # defaults to false if not specified so resources can be inspected to debug failures during validation
destroy_workspace_on_failure: false # defaults to false if not specified so schematics workspace can be inspected to debug failures during validation
import_only: false # defaults to false - set to true if you do not want to do any validation, but be aware offering can't be publish if not validated
validation_rg: validation # the resource group in which to do validation in. Will be created if does not exist. If not specified, default value is 'validation'
# scc details needed if your offering is claiming any compliance controls
scc:
# must be an instance in the same account the validation is being done in
instance_id: 1c7d5f78-9262-44c3-b779-b28fe4d88c37
region: us-south
# pre_validation: tests/scripts/pre-validation.sh # optionally run a command before validation runs
# post_validation: tests/scripts/post-validation.sh # optionally run a command after validation completes
- name: deploy-arch-ibm-storage-scale # must match the offering name in the ibm_catalog.json
kind: solution
catalog_id: 90717ada-be34-4b82-a0d9-0f225f8dbd76
offering_id: 33105573-84df-4279-9efa-48887456fa6d
# list all of the variations (flavors) you have included in the ibm_catalog.json
variations:
- name: Cluster-with-Scale
mark_ready: false # have pipeline mark as visible if validation passes
install_type: fullstack # ensure value matches what is in ibm_catalog.json (fullstack or extension)
destroy_resources_on_failure: false # defaults to false if not specified so resources can be inspected to debug failures during validation
destroy_workspace_on_failure: false # defaults to false if not specified so schematics workspace can be inspected to debug failures during validation
import_only: false # defaults to false - set to true if you do not want to do any validation, but be aware offering can't be publish if not validated
validation_rg: validation # the resource group in which to do validation in. Will be created if does not exist. If not specified, default value is 'validation'
# scc details needed if your offering is claiming any compliance controls
scc:
# must be an instance in the same account the validation is being done in
instance_id: 1c7d5f78-9262-44c3-b779-b28fe4d88c37
region: us-south
# pre_validation: tests/scripts/pre-validation.sh # optionally run a command before validation runs
# post_validation: tests/scripts/post-validation.sh # optionally run a command after validation completes