Conversation
For the avocado-deploy-rpi SDK deploy hook to work, ssh must be available to the SDK, and fwup must be available on the target. Therefore, add nativesdk-openssh-ssh as an SDK dependency and fwup as an application dependency. Tested on a RPI CM5 via the command "avocado deploy -r dev -d <ip address>". Signed-off-by: Mitchell Tasman <tasman@leaflabs.com>
|
These config files are leftover references previously used by come of the test cases as fixtures. Up to date copies of configs are found at avocado-linux/avocado-os/reference. thanks for fixing this up |
|
@mobileoverlord: Is it entirely true that the configs are unused today? If I follow the provisioning docs, e.g.: https://docs.peridio.com/hardware/raspberry-pi/raspberry-pi-5/provision, I get an avocado.toml that looks a lot like avocado-cli/configs/raspberry-pi/raspberrypi-5.toml In order to get the version from avocado-os/references, I need to add a --reference argument, e.g.: but I'm unclear how anyone following the existing documentation would know to do that. Is "avocado init" now supposed to be defaulting to "--reference dev"? For me, with Avocado CLI 0.16.0, it is not. |
2 participants
For the avocado-deploy-rpi SDK deploy hook to work, ssh must be available to the SDK, and fwup must be present on the target.
Therefore, add nativesdk-openssh-ssh as an SDK dependency and fwup as an application dependency.
Tested on a RPI CM5 via the command "avocado deploy -r dev -d ".