docs: note about removal of record/server new
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:
parent
f2f335d4da
commit
14e9da8d82
@ -40,6 +40,11 @@ abra upgrade --rc
|
|||||||
`cd ~/.abra/catalogue && git checkout .` to get `abra` to stop complaining about
|
`cd ~/.abra/catalogue && git checkout .` to get `abra` to stop complaining about
|
||||||
unstaged changes.
|
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`
|
### `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.
|
- **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.
|
||||||
|
Loading…
x
Reference in New Issue
Block a user