-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update strategy and handover timeout not being detect with BALENA_ prefix #735
Comments
I'm just documenting this issue. We don't mind that this exists because this is just for backwards compatibility. If you encounter this issue you must set the update strategy in your services as a label in the docker-compose file: https://www.balena.io/docs/reference/supervisor/docker-compose/#labels. |
Reopening this issue since there is no resolution either in the documentation or the API. Although it is true that the way the supervisor understands release strategies is through labels, the we have also discussed having application level release strategies (see balena-os/balena-supervisor#1103) and this method would be compatible with that, so I'm not entirely sure we want to move away from this method. The simplest short term solution seems to be to update the code linked by @20k-ultra including the |
[inspaya] This issue has attached support thread https://jel.ly.fish/b1dd2ce2-1a3f-4809-b9bc-b821fa7b9073 |
[Documentation](https://www.balena.io/docs/learn/deploy/release-strategy/update-strategies/#controlling-the-update-strategy) mentions `BALENA_SUPERVISOR_UPDATE_STRATEGY` config var as a way to set the update strategy, but this var has no effect as there is no transform setup for it (there is only one for for `RESIN_` prefix). Change-type: patch Closes: #735
[Documentation](https://www.balena.io/docs/learn/deploy/release-strategy/update-strategies/#controlling-the-update-strategy) mentions `BALENA_SUPERVISOR_UPDATE_STRATEGY` config var as a way to set the update strategy, but this var has no effect as there is no transform setup for it (there is only one for for `RESIN_` prefix). Change-type: patch Closes: #735
[Documentation](https://www.balena.io/docs/learn/deploy/release-strategy/update-strategies/#controlling-the-update-strategy) mentions `BALENA_SUPERVISOR_UPDATE_STRATEGY` config var as a way to set the update strategy, but this var has no effect as there is no transform setup for it (there is only one for for `RESIN_` prefix). Change-type: patch Closes: #735
[Documentation](https://www.balena.io/docs/learn/deploy/release-strategy/update-strategies/#controlling-the-update-strategy) mentions `BALENA_SUPERVISOR_UPDATE_STRATEGY` config var as a way to set the update strategy, but this var has no effect as there is no transform setup for it (there is only one for for `RESIN_` prefix). Change-type: patch Closes: #735
[Documentation](https://www.balena.io/docs/learn/deploy/release-strategy/update-strategies/#controlling-the-update-strategy) mentions `BALENA_SUPERVISOR_UPDATE_STRATEGY` config var as a way to set the update strategy, but this var has no effect as there is no transform setup for it (there is only one for for `RESIN_` prefix). Change-type: patch Closes: #735
[Documentation](https://www.balena.io/docs/learn/deploy/release-strategy/update-strategies/#controlling-the-update-strategy) mentions `BALENA_SUPERVISOR_UPDATE_STRATEGY` config var as a way to set the update strategy, but this var has no effect as there is no transform setup for it (there is only one for for `RESIN_` prefix). Change-type: patch Closes: #735
There is a legacy device configuration called
SUPERVISOR_UPDATE_STRATEGY
andSUPERVISOR_HANDOVER_TIMEOUT
which are prefixed withRESIN_
or nowBALENA_
however it only works withRESIN_
. This is because ofopen-balena-api/src/features/device-state/routes/state.ts
Lines 200 to 205 in 17f79c6
RESIN_
.The text was updated successfully, but these errors were encountered: