-
Notifications
You must be signed in to change notification settings - Fork 27
Description
Severity
Medium
What release version, tag or commit-hash did you use?
v0.1.2
Current Behavior
I tried to link my forked SDK repository to velocitas template, I have updated my velocitas.json variable with "gitLocation": "your custom location without the repo-name" and using latest version of devenv-devcontainer-setup v2.6.2 but it is not able to pick the SDK repo which is linked instead it picks default SDK repo.
I have also updated velocitas-sdk version in requirements.txt file
Note: forked sdk repo name is "vehicle-app-python-sdk"
Velocitas.json:
Steps to Reproduce
- Added gitLocation variable in velocitas.json
- Updated velocitas-sdk version in requirements.txt file
- Build dev container or build an image
- Default sdk is linked instead of custom SDK
Expected Behavior
Custom SDK repository needs to be downloaded and used as library by vehicle app flexibly from velocitas.json.
Possible Solution
I have come up with workaround to link my custom repo by directly specifying the package in requirments.txt. Ideally this is not the solution it should be linked via velocitas.json itself.
Additional Information
No response
Code of Conduct
- I agree to follow this project's "Code of Conduct".

