Skip to content
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

Including files in desired state communicated to VUM #43

Open
eriksven opened this issue May 5, 2023 · 1 comment
Open

Including files in desired state communicated to VUM #43

eriksven opened this issue May 5, 2023 · 1 comment

Comments

@eriksven
Copy link
Contributor

eriksven commented May 5, 2023

Hello,

I would like to setup a fresh Leda installation for my specific use case. This involves adding further files which should be mounted by some of the executed containers. One example would be an JSON-file with an extended vehicle model to by mounted by the Kuksa.Val databroker container.

Is there a way to include such files or the download of such files in the desired state configuration one can send to the VUM (https://eclipse-leda.github.io/leda/docs/device-provisioning/vehicle-update-manager/)?

Or is there another "Leda-way" to get such files to the Leda host-system without the need to build a new custom Leda image and apply it through the VUM and Self-Update-Agent?

@vasilvas99
Copy link
Contributor

vasilvas99 commented May 11, 2023

Hi, @eriksven
As mentioned in #42, we are still waiting on the updated version of VUM to get an OSS release and such updates should ideally be handled through the desired state manifest.
That said, the Leda Distro Quickstart Images (esp. the 0.1.0+ releases) are supposed to be a development environment, so from my point of view it is okay to ssh/scp files to the /data partition as needed. For example you can add your extended vehicle model JSON inside a custom directory under /data and then update the databroker manifest accordingly (should be automatically picked-up and re-deployed on change).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants