sdk hosting test

[plorenz]

• Add fablab test for SDK hosting
• update for fablab changes

[andrewpmartinez]

The OpenAPI Specs all need to be updated w/ the new HTTP Status code that can return. Depending on the client, if an invalid code is returned, it might panic or return a useless "unexpected HTTP status code" error with no way to see the actual response. At best, you get the raw response and hit a generic handler in the end client's code.

This is also not backward compatible w/ older generated clients. So, a version change is also suggested. This also will affect the GoSDK.

[plorenz]

The OpenAPI Specs all need to be updated w/ the new HTTP Status code that can return. Depending on the client, if an invalid code is returned, it might panic or return a useless "unexpected HTTP status code" error with no way to see the actual response. At best, you get the raw response and hit a generic handler in the end client's code.

This is also not backward compatible w/ older generated clients. So, a version change is also suggested. This also will affect the GoSDK.

There's a PR up for updating the edge-api project and the fabric API has been updated here. Should we bump the version to 0.31.0?

[andrewpmartinez]

The OpenAPI Specs all need to be updated w/ the new HTTP Status code that can return. Depending on the client, if an invalid code is returned, it might panic or return a useless "unexpected HTTP status code" error with no way to see the actual response. At best, you get the raw response and hit a generic handler in the end client's code.
This is also not backward compatible w/ older generated clients. So, a version change is also suggested. This also will affect the GoSDK.

There's a PR up for updating the edge-api project and the fabric API has been updated here. Should we bump the version to 0.31.0?

I would say yes.

[plorenz]

The OpenAPI Specs all need to be updated w/ the new HTTP Status code that can return. Depending on the client, if an invalid code is returned, it might panic or return a useless "unexpected HTTP status code" error with no way to see the actual response. At best, you get the raw response and hit a generic handler in the end client's code.
This is also not backward compatible w/ older generated clients. So, a version change is also suggested. This also will affect the GoSDK.

There's a PR up for updating the edge-api project and the fabric API has been updated here. Should we bump the version to 0.31.0?

I would say yes.

Version has been bump to 0.31