This directory contains a list of commonly-used, tested, operations files.

Unless otherwise stated, they can be combined in any permutation and in any order.

This operations file registers routes with the Cloud Foundry router which point to the dashboard pages hosted by the proxies deployed as part of cf-mysql-release.

To enable integration of the MySQL database with Cloud Foundry (as a Cloud Foundry service), you should include the add a broker operations file, as well as the register the proxy route operations file.

Used when the dependent deployments (i.e. Cloud Foundry) do not expose properties via cross-deployment links.

For example, many configurations of cf-release (including the provided spiff manifest generation) do not support cross-deployment links without manual modifications to the manifest, whereas deploying Cloud Foundry via cf-deployment exposes properties like NATS config by default.

Using this operations file will require you to provide your own values for these properties which would otherwise be provided via links, e.g. NATS.

Example usage:

-o disable-smoke-tests-cross-deployment-links.yml \
-o disable-broker-route-registrar-cross-deployment-links.yml \
-o disable-proxy-route-registrar-cross-deployment-links.yml \

-v nats="{password: some-nats-password, user: nats, port: 4222, machines: [10.0.31.191]}" \
-v admin_username=admin \
-v admin_password=password \
-v api_url=api.mycf.com \
-v app_domains=[mycf.com] \
-v skip_ssl_validation=true \

Provides a value for the property cf_mysql.host property, which is host the broker provides to applications via service instance bindings.

Typically this is a FQDN pointing to a load balancer or some other mechanism to achieve HA (e.g. DNS, floating virtual IPs etc).

Example usage:

-o configure-broker-load-balancer.yml \

-v cf_mysql_host=my-load-balancer-url