Add Postgres upgrade advice
All checks were successful
continuous-integration/drone/push Build is passing
All checks were successful
continuous-integration/drone/push Build is passing
This commit is contained in:
@ -402,6 +402,25 @@ You can also add release notes for the next release into a special file `release
|
|||||||
|
|
||||||
This feature is only available in the > 0.9.x series of `abra`.
|
This feature is only available in the > 0.9.x series of `abra`.
|
||||||
|
|
||||||
|
## How do I know whether to accept version upgrades when running `abra recipe upgrade <something>`?
|
||||||
|
|
||||||
|
### Postgres
|
||||||
|
|
||||||
|
Beware major Postgres version updates!
|
||||||
|
|
||||||
|
"Major" updates are ones where the first number changes, for example 14 to 15 (or 14.1 to 15.1).
|
||||||
|
|
||||||
|
Postgres cannot update itself, so accepting major version upgrades can break existing app deployments.
|
||||||
|
|
||||||
|
To check if a recipe can handle upgrades:
|
||||||
|
|
||||||
|
1. Check whether the recipe is using the `pgautoupgrade` image.
|
||||||
|
2. Check whether the recipe contains a custom postgres entrypoint, `entrypoint.postgres.sh`.
|
||||||
|
|
||||||
|
If neither #1 nor #2 is true, **do not include a "major" postgres upgrade in a recipe upgrade**.
|
||||||
|
|
||||||
|
Feel welcome to ask for help in #coopcloud-tech:matrix.autonomic.zone
|
||||||
|
|
||||||
## How do I generate the recipe catalogue
|
## How do I generate the recipe catalogue
|
||||||
|
|
||||||
To generate an entire new copy of the catalogue:
|
To generate an entire new copy of the catalogue:
|
||||||
|
Reference in New Issue
Block a user