Closed pdellaert closed 9 years ago
Temporary fix (but it's not the clean way) possible, see (closed) pull request #2 . Final solution will have to come from developers, as i don't know the entire codebase structure ;)
Proposed fix without touching Bambou, but using vspk instead: https://github.com/pdellaert/vspk/commit/e13744f1d252564619d3cccf650dbecbf23618ab
Up to you guys to decide if you want to pull it or not.
@pdellaert,
I am currently working on a clean fix. I'll keep you updated.
Great! Thank you :)
Was just wondering if a clean/permanent fix has been implemented yet?
This is also affecting the CLI, btw:
[root@ent-43001 ~]# vsd list vrs --in vsc d5e4c8a5-53f1-4254-95d8-549f1ab2f5f8
[Error] Unknown object named vrs
[root@ent-43001 ~]# vsd list vrss --in vsc d5e4c8a5-53f1-4254-95d8-549f1ab2f5f8
[Error] Unknown object named vrs
[root@ent-43001 ~]# vsd list vrsss --in vsc d5e4c8a5-53f1-4254-95d8-549f1ab2f5f8
[Success] 5 vrss have been retrieved
If you request the VRSs from a VSC. It will return an error: 400 Bad request.
It is using the wrong URL to fetch the VRSs (.../vscs/ID/vrs instead of .../vscs/ID/vrss)
Code example:
Return: