Closed xouillet closed 10 months ago
second on this one.
when I am looking at it, it's cli that sends stringified contract object, while api-server only accepts object which leads to one rejected request. so I guess it's the cli part needs to be updated.
Yes, modifying the balena-cli
source make it works, but it means that there is a difference between cloud api and openbalena api...
I've encountered this error as well, and think it can easily be handled by open-balena-api
by checking for contracts provided as a string, and parsing the object from it. I'm submitting a PR to this effect.
The PR can be found here: https://github.com/balena-io/open-balena-api/pull/1468
This should be fixed as of v14.17.0
Hi,
I'm trying to switch from balena cloud server to a self-hosted open-balena instance.
When deploying a release with a
balena.yml
file, I get the errorThe exact same deployment works without issue on cloud balena.
If I delete the
balena.yml
file, the release is correctly created on openbalena (but without thesemver
and other information frombalena.yml
obviously...).