I tried deploying bbl with vpc_cidr="10.0.0.0/22" (anonymized IP subnet here) configured in vars/something.tfvars.
The bbl plan step went through perfectly fine, but then bbl up looked like this:

$ bbl up
step: terraform init
step: terraform apply


Executor apply: Some output has been redacted, use `bbl latest-error` to see it or run again with --debug for additional debug

Is your feature request related to a problem? Please describe.
Today CFCR is only deployed with Flannel but we're in need of using Calico for creating network policies to use CFCR in PCI compliant environments.

Describe the solution you'd like
It would be great to either include an option within the CFCR deployment process to select which network plugin to use or post a README for doi

+ telegraf:
+   influxdb:
+     database: concourse
+     password: fu6aytlsfpkrneowda3b
+     url: http://10.0.0.8:8086
+     username: admin

Spotted this in one of the system test runs.

I want to be able to specify a variable value when deploying kubecf, e.g.

bosh deploy ... -v cf-admin-password=cant-guess-this

I assumed that there is a mechanism already, as the main point of using variables is to make it easier for users to configure settings without having to write ops-files. Indeed often ops-files are provided upstream, that add additional variables to make the

Disk creation failed in Minikube environment. What could be the reason?

./deployment/minikube/scripts/create-env.sh
...
...
Started deploying
  Waiting for the agent on VM '54c7a391-5c97-4a16-60e3-3e7ada55e156'... Finished (00:00:00)
  Stopping jobs on instance 'unknown/0'... Finished (00:00:00)
  Deleting VM '54c7a391-5c97-4a16-60e3-3e7ada55e156'... Finished (00:00:01)
  Creating V

Done with cloudfoundry/bosh-openstack-cpi-release#117 but not mentioned in the job spec.

See #231 – it seems like this could help people achieve their goals.

Now (v3.8) the cluster name is exported by prometheus_exporter as rabbitmq_identity_info.rabbitmq_cluster.

By default the cluster name is root@localhost and can be changed using "Management UI".

Is it a good idea to set it using a deployment manifest?

For

Hi BPM, Garden here.

TL;DR
Rootless garden bosh-lite CF deployment fails with cf-deployment 11.0.0 and rootless containers enabled. The failure is caused by the garden job failing to start. We think that this is a regression in BPM 1.1.1, hence this bugreport.
Note that the fail

Hi @xoebus & all,

I'm in the process of reviewing this exemplar-release documentation before contributing additions here, like examples of BPM jobs (a donation from the training courses delivered by my company Gstack), and correct drain scripts for cluster 'scale-in' condition, i.e. permanent removal of stateful cluster members.

About post-deploy, I recently saw that [the RabbitMQ re

Expected behavior

https://github.com/orange-cloudfoundry/cf-ops-automation/blob/develop/docs/reference_dataset/template_repository/hello-world-root-depls/bosh-deployment-sample/deployment-dependencies.yml should illustrate usage of the errand

Observed behavior

errand support is documented into https://github.com/orange-cloudfoundry/cf-ops-automation#bosh-deployment-resources-templat