From 14e9da8d821ca93e85b9a7193b4fef0bc1db62fe Mon Sep 17 00:00:00 2001 From: decentral1se Date: Thu, 14 Sep 2023 16:50:37 +0200 Subject: [PATCH] docs: note about removal of record/server new --- docs/abra/upgrade.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/abra/upgrade.md b/docs/abra/upgrade.md index 5b93157..fd79d10 100644 --- a/docs/abra/upgrade.md +++ b/docs/abra/upgrade.md @@ -40,6 +40,11 @@ abra upgrade --rc `cd ~/.abra/catalogue && git checkout .` to get `abra` to stop complaining about unstaged changes. +- `abra record ...` & `abra server new` have been removed! Following a usage poll, these + features were not being relied on. They were also alpha prototypes which we + feel can be reconsidered once other more critical parts of Abra are more + stable. + ### `0.6.x-beta` -> `0.7.x-beta` - **ALERTA, ALERTA**, security related issue: all `$domain.env` env vars are now exposed to the deployment via the `app` service container. Each `FOO=BAR` is exported within the context of the container. If you have any privately committed secrets in your `.env` files, please migrate them to the `secrets: ...` configuration in the recipe. This change was made to facilitate tooling which can support auto-upgrading of apps in a deployment.