From 6e2674493bebf50657f9e483ad57fd40b031b706 Mon Sep 17 00:00:00 2001 From: Jochen Ehret Date: Thu, 12 Mar 2026 13:10:30 +0100 Subject: [PATCH] Document ops files order for "use-postgres.yml" file --- operations/README.md | 2 +- operations/use-postgres.yml | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/operations/README.md b/operations/README.md index c13868e8e..28f4ba920 100644 --- a/operations/README.md +++ b/operations/README.md @@ -77,7 +77,7 @@ This is the README for Ops-files. To learn more about `cf-deployment`, go to the | [`use-latest-windows2019-stemcell.yml`](use-latest-windows2019-stemcell.yml) | Use the latest `windows2019` stemcell available on your BOSH director instead of the one in `windows2019-cell.yml` | Requires `windows2019-cell.yml` | **NO** | | [`use-metric-store.yml`](use-metric-store.yml) | Adds a single-node metric store. | | **NO** | | [`use-operator-provided-router-tls-certificates.yml`](use-operator-provided-router-tls-certificates.yml) | Allows an operator to provide their own certificates for the gorouter by providing variables [`router_ssl_pem`](example-vars-files/vars-use-operator-provided-router-tls-certificates.yml) | This is required if using AWS Network Load Balancers. | **YES** | -| [`use-postgres.yml`](use-postgres.yml) | Replaces the MySQL instance group with a postgres instance group. **Warning**: this will lead to total data loss if applied to an existing deployment with MySQL or removed from an existing deployment with postgres. | | **YES** | +| [`use-postgres.yml`](use-postgres.yml) | Replaces the MySQL instance group with a postgres instance group. **Warning**: this will lead to total data loss if applied to an existing deployment with MySQL or removed from an existing deployment with postgres. | If combined with [`use-compiled-releases.yml`](use-compiled-releases.yml), you must apply this ops file **after** `use-compiled-releases.yml`. | **YES** | | [`use-trusted-ca-cert-for-apps.yml`](use-trusted-ca-cert-for-apps.yml) | Injects the CA specified with `trusted_cert_for_apps` into the Diego `rep` job's trust store and cf-deployment's default root filesystem | Applications that *explicitly* look in the canonical location (`/etc/cf-system-certificates`) will trust certificates signed by the given CA, regardless of filesystem. Applications that use the default root filesystem will trust certificates signed by the given CA *implicitly*.
Please see the [documentation](https://docs.cloudfoundry.org/running/trusted-system-certificates.html) for information about configuring additional trusted CA certificates. | **NO** | | [`use-offline-windows2019fs.yml`](use-offline-windows2019fs.yml) | Use the offline version of [windows2019fs-release](https://github.com/cloudfoundry/windows2019fs-release) | Requires `windows2019-cell.yml`. Suitable for environments without internet access. Follow instructions [here](https://github.com/cloudfoundry/windows2019fs-release/blob/master/README.md) to upload the release prior to deploying. | **NO** | | [`use-online-windows2019fs.yml`](use-online-windows2019fs.yml) | Use the windows2019fs job from the online version of [windowsfs-release](https://github.com/cloudfoundry/windowsfs-online-release) | Requires `windows2019-cell.yml`. Requires environment to have internet access. | **YES** | diff --git a/operations/use-postgres.yml b/operations/use-postgres.yml index 81cc28adc..2520b96f6 100644 --- a/operations/use-postgres.yml +++ b/operations/use-postgres.yml @@ -1,3 +1,4 @@ +# Note: If combined with `use-compiled-releases.yml`, you must apply `use-postgres.yml` after applying `use-compiled-releases.yml`. - type: replace path: /releases/- value: