From 395b52691f98947f5b5f1eff3a991161c1e1d6fe Mon Sep 17 00:00:00 2001 From: decentral1se Date: Fri, 29 Aug 2025 17:03:04 +0200 Subject: [PATCH] docs: version warning and drop --ignore-env-version --- docs/maintainers/handbook.md | 2 +- docs/operators/handbook.md | 12 ++++++------ 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/maintainers/handbook.md b/docs/maintainers/handbook.md index 0113459..7d51f3e 100644 --- a/docs/maintainers/handbook.md +++ b/docs/maintainers/handbook.md @@ -413,7 +413,7 @@ You can also add release notes for the next release into a special file `release !!! warning "Watch out for old versions of `abra` 🚧" - 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 `? diff --git a/docs/operators/handbook.md b/docs/operators/handbook.md index 0c88f4d..d338866 100644 --- a/docs/operators/handbook.md +++ b/docs/operators/handbook.md @@ -512,7 +512,7 @@ abra app secret insert localhost ssl_key v1 localhost.key -f !!! warning "Watch out for old versions of `abra` 🚧" - This feature is only available in the > 0.10.x series of `abra`. + This feature is only available in the >= 0.10.x series of `abra`. It is possible to specify a remote recipe in your `.env` file: @@ -532,7 +532,7 @@ $ABRA_DIR/recipes/mygit_org_myorg_cool-recipe !!! warning "Watch out for old versions of `abra` 🚧" - This feature is only available in the > 0.10.x series of `abra`. + This feature is only available in the >= 0.10.x series of `abra`. If you `abra app new`/`abra app deploy`/`abra app upgrade`/`abra app rollback`, the version that is deployed will be written to your app `.env` file. You can @@ -553,13 +553,13 @@ TYPE=custom-html:1.7.1+1.27.2 This `.env` version is then used as the recipe checkout version for **all** `abra` operations afterwards unless you specify otherwise on the command-line -with `[version]` `--chaos/-C` or `--ignore-env-version/-i`. +with `[version]` `--chaos/-C` or `--latest/-l`. ## How is the new deployment version determined? !!! warning "Watch out for old versions of `abra` 🚧" - This feature is only available in the > 0.10.x series of `abra`. + This feature is only available in the >= 0.10.x series of `abra`. ### `.env` version @@ -569,7 +569,7 @@ deployment overview. This `.env` version is then used as the recipe checkout version for **all** `abra` operations afterwards unless you specify otherwise on the command-line -with `[version]` `--chaos/-C` or `--ignore-env-version/-i`. +with `[version]` `--chaos/-C` or `--latest/-l`. ### `abra app deploy` @@ -592,7 +592,7 @@ The version is chosen using the following priority logic. 1. deployed app 1. recipe catalogue (if undeployed) -Use `--ignore-env-version/-i` to deploy the latest release version or commit. +Use `--latest/-l` to deploy the latest release version or commit. In all cases 3-5, the app `.env` version is **ignored** as a version candidate.