// List of deployments expected to be created via Helm
const helmDeps =
[
- 'dcae-cloudify-manager'
+ 'dcae-cloudify-manager',
+ 'dcae-config-binding-service'
];
// List of deployments expected to be created by CM at boot time
const bootDeps =
[
- 'dep-config-binding-service',
'dep-deployment-handler',
'dep-inventory',
'dep-service-change-handler',
{
"name": "k8s-healthcheck",
"description": "DCAE healthcheck server",
- "version": "1.2.1",
+ "version": "1.2.2",
"main": "healthcheck.js",
"author": "author",
"license": "(Apache-2.0)"
<groupId>org.onap.dcaegen2.deployments</groupId>
<artifactId>healthcheck-container</artifactId>
<name>dcaegen2-deployments-healthcheck-container</name>
- <version>1.2.1</version>
+ <version>1.2.2</version>
<url>http://maven.apache.org</url>
<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
# Deploy platform components
# Allow for some parallelism to speed up the process. Probably could be somewhat more aggressive.
-# config_binding_service and pgaas_initdb needed by others, but can execute in parallel
-deploy config_binding_service k8s-config_binding_service.yaml k8s-config_binding_service-inputs.yaml &
-CBS_PID=$!
deploy pgaas_initdb k8s-pgaas-initdb.yaml k8s-pgaas-initdb-inputs.yaml &
PG_PID=$!
-wait ${CBS_PID} ${PG_PID}
+wait ${PG_PID}
# inventory, deployment_handler, and policy_handler can be deployed simultaneously
deploy inventory k8s-inventory.yaml k8s-inventory-inputs.yaml &
INV_PID=$!
BLUEPRINTS=\
"
-k8s-config_binding_service.yaml \
k8s-deployment_handler.yaml \
k8s-holmes-engine.yaml \
k8s-holmes-rules.yaml \
<groupId>org.onap.dcaegen2.deployments</groupId>
<artifactId>k8s-bootstrap-container</artifactId>
<name>dcaegen2-deployments-k8s-bootstrap-container</name>
- <version>1.4.5</version>
+ <version>1.4.6</version>
<url>http://maven.apache.org</url>
<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>