summaryrefslogtreecommitdiffstats
path: root/recipes-sota/aktualizr/aktualizr-shared-prov.bb
Commit message (Collapse)AuthorAgeFilesLines
* aktualizr: Don't put unused configs in the image.feat/2020.10Patrick Vacek2020-11-031-1/+1
| | | | | | | | | | | | | | | | | Because every aktualizr package was depending on aktualizr-configs, all of the default configs were getting installed to /usr/lib/sota, despite that by default none of them were ever used on the device. That dependency has been removed. The provisioning recipes still install the recipes they need to the default location that aktualizr actually uses (/usr/lib/sota/conf.d). If you want to use anything else, a specific recipe should be created to do so. This change rendered the aktualizr-host-tools package useless, so it has been removed. Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
* sota_sanity.bbclass: introduce sota_check_boolean_variableMing Liu2020-05-111-1/+1
| | | | | | | | | | The current sanity check are too strict for some boolean variables, introduce sota_check_boolean_variable to allow a boolean value to be set like yes/y/true/t/1 or no/n/false/f/0. Also change to use oe.types.boolean to check their values. Signed-off-by: Ming Liu <ming.liu@toradex.com>
* aktualizr: use SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS for config recipes.Patrick Vacek2019-10-171-0/+3
| | | | | | | | | | | | | This is a bit of a compromise. These recipes are allarch, since they do not depend on an architecture, but they depend on aktualizr, which is definitely not allarch. Therefore, we must tell bitbake not to treat the aktualizr architecture as a dependency of these recipes. However, this means that if one of the config files changes in the aktualizr repo, we need to bump the version of the recipe that uses it to make sure bitbake picks up that change. Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
* aktualizr: fix secondary recipes' dependencies.Patrick Vacek2019-10-171-4/+4
| | | | | | | Most do not need to depend on aktualizr-native and do not need to be rebuilt if the credentials change. Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
* Rename provisioning methods.Patrick Vacek2019-06-051-0/+43
"Autoprovisioning" or "automatic provisioning" is now known as "shared credential provisioning". "Implicit provisioning" is now known as "device credential provisioning". "HSM provisioning" was always a misnomer, so it is now refered to as "device credential provisioning with an HSM". This includes a bump of the aktualizr version as well. Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>